31 Jan
2003
31 Jan
'03
2:27 p.m.
The worst situation we can end up in if we go ahead
with XAP is two
plugin APIs on Linux; XAP and a new, totally incompatible API. That's
still a lot better than the *current* situation on Windows and Mac
OS.
Given the nature of vested interest, this is probably the best
situation, not the worst. Don't wait. The only reason to delay is if
you actually believe that a unified approach is not just possible, but
probable. Closed developers might agree to a closed, members only,
approach but a true unification would require either presently closed
developers to abandon the idea of trade secrets, or open developers to
abandon the gpl. Neither is likely. If you are into it, just go ahead.
Tom
31 Jan
31 Jan
3:16 p.m.
New subject: [linux-audio-dev] The future of XAP? (was: fruityloops on linux?)
On Fri, Jan 31, 2003 at 11:21:36 -0800, Tom wrote:
I think thats overly negative, theres a worl of difference between open
APIs and open source plugins.
- Steve
The worst
situation we can end up in if we go ahead with XAP is two
plugin APIs on Linux; XAP and a new, totally incompatible API. That's
still a lot better than the *current* situation on Windows and Mac
OS.
Given the nature of vested interest, this is probably the best
situation, not the worst. Don't wait. The only reason to delay is if
you actually believe that a unified approach is not just possible, but
probable. Closed developers might agree to a closed, members only,
approach but a true unification would require either presently closed
developers to abandon the idea of trade secrets, or open developers to
abandon the gpl. Neither is likely. If you are into it, just go ahead.
8004
days inactive
8004
days old
linux-audio-dev@lists.linuxaudio.org
1 comments
2 participants
participants (2)
-
Steve Harris -
Tom