> can you name any commercial audio applications for
not yet... but tying the success of your product to
the progress of a relitavely new open source project
is a bad idea in some cases. It depends on the
timeframe and situation.
Say you have 3 months to deliver an audio app for both
windows and linux. If you take longer than that,
you'll have to start going to work again or get
evicted (I swear, this is a hypothetical situation ;P)
JACK may or may not be ready by then, but if you use
agile programming practices and an abstraction layer,
your app will be ready for JACK or whatever new pops
up, even at the last minute!
> JACK has already been ported to OS X,
Good. I'd code my app for OS X too if I could afford a
mac.. mayhaps my next big purchase? Any plans for
other unixen? I know VST is avail for SGI...
> thankfully, a quick
hehehe, no need to go further.
My conclusion before I shut up on this matter: in real
life relationships, put all your eggs in one basket,
have faith in said person, yadda yadda. In APIs &
OSen, be like a distrustful whore! put your eggs in
every basket you can find! jump ship at the first sign
of new opportunity. I'd make an exception though that
I generally want linux to be sucessful, so I'll write
for linux even though there isn't much of a market for
linux audio apps... yet ;)
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search