Re: Cocoa and AudioUnits?
Re: Cocoa and AudioUnits?
- Subject: Re: Cocoa and AudioUnits?
- From: john <email@hidden>
- Date: Sat, 25 Jan 2003 21:48:58 +0000
Hi Michael,
I'm glad you support Cocoa! But I don't think Andy's simply complaining
that he can't use his favourite language. I certainly don't mind a
transitionary period, but what I fear is that even besides any
technical benefits Cocoa may provide, you're just opening the door for
legacy APIs used by a new API to become a standard. You're also adding
complexity to pulling off the final transition without any more
problems.
Plus, I question whether for Apple to create "easier" support for using
Cocoa views in Carbon apps is a big job. Since Andy was able to come up
with a solution as a single developer, I'm sure the Carbon development
team at Apple could have come up with "something", and most certainly
better (no offence to Andy, of course!).
-- John
As a Cocoa fan, I've been watching this discussion with some interest.
But I would like to say something here.
I'd personally _love_ it if I could write everything in Objective-C.
But I think Bill was trying to say that it's just not practical right
now to have the UIs in Cocoa.
Bill is absolutely right: _all_ of the major hosting apps are written
in Carbon. You can't _easily_ host a Cocoa view in a Carbon app - not
right now. Therefore, AudioUnit UIs are Carbon - right now.
Any time you do a large software project (or any project at all, for
that matter), you find that there are features that you would like it
to do, but that you don't have time, or maybe ability, to implement.
Sometimes you have to make hard decisions, and throw things out. This
doesn't look to have been a hard decision.
One day things may change. As time goes on, and the platform continues
to develop, it may become practical to write AudioUnit UIs in Cocoa.
I'm greatly looking forward to that day.
But reality is that people would like to be making music with
AudioUnits _now_. Should we make them wait longer so we can use our
favorite languages and toolkits?
Apple, like most companies, is staffed with humans, and only a finite
number of them. They can't do everything they would like to do as
quickly as they would like to do it, and there's no way they will ever
do it as quickly as everyone else would like them to do it. It simply
takes time to make things.
Anybody who doesn't understand this is either nuts, not working, or in
for some hard lessons.
Guys, this _is_ the World's Coolest Computer Audio System. Let's not
go hinting at "corporate politics" when the developers don't do
everything we want right when we want them to do it.
----
Michael Ashton <email@hidden>
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.