[Pipet Devel] ideas for a smaller piper core

Jean-Marc Valin jmvalin at locusdialogue.com
Mon May 28 14:21:25 EDT 2001

> This has nothing to do with liking or disliking any one part of Piper, and it
> has everything to do with modularity.  Jarl once said that someone somewhere
> may want to swap out his BL for another one.  Should Piper be modular enough
> to allow that?  I think so.  And I really don't care if something thinks that
> my Pied (Desktop) is sh*t and wants to use something else.

I've got one problem with that: interoperability. Since the idea of
Piper is about distributed computing, you want (almost) the same Piper
to run on all the machines. If you have 4 different DL's, 3 BL's and 5
PL's, you get 60 different Piper configurations and a total mess. It's
impossible to do QA, and you can only use Piper on 1/60th of the
machines... Modularity is nice, but to much of a good thing is bad.

BTW, correct me if I'm wrong but your initial post was about a
non-distributed Piper desktop... well for that, all you'd need is
Overflow with (maybe) a more user-friendly GUI. ...and you don't even
need the DL/BL. Those are for distributed computing.


More information about the Pipet-Devel mailing list