On Mon, 2011-02-21 at 20:56 +0000, Fons Adriaensen wrote:
Which is why yours is a poor solution. It loses much, and gains little
if anything. Making a UNIX only plugin or UI is fine. Making a UNIX
only plugin API is (in this case) stupid.
You /can/ implement "I don't give a damn about anything but "
plugin UIs (or hosts) right now, by design. I have always strongly
advocated this. You can't, however, use some nonexistent authority to
force all the other developers to agree - many (and in this case
virtually all) don't. Try and make a monolithic kitchen sink plugin API
like that and watch as everyone outright rejects the entire thing
instead of little replaceable slivers of it...
Yours is a valid perspective for UI and host authors. It is a terrible
one from the API designer perspective. The good design lets you and
others work only with your preferred technology - and interoperate with
others with different tastes. This is possible, feasible, and makes
more developers and users happy. It is, in other words, an objectively
much better solution.
Linux-audio-dev mailing list