Re: Cocoa and future
Re: Cocoa and future
- Subject: Re: Cocoa and future
- From: tahome izwah <email@hidden>
- Date: Fri, 20 Feb 2009 18:45:22 +0100
2009/2/20 john smith <email@hidden>:
>
> I have no problem with new API's. I'm not too happy with being forced to
> learn a new language when I'm only using it to glue things together though.
"Glue something together"? That doesn't sound like a good strategy for
software development to me, if you don't mind my saying.
> And finally I'm not happy with Apple continuously telling me that I should
> be happy to get this extra work. Because no matter how you look at it, then
> I have code that works now, and which will not work at some point in the
> future. That is extra work.
Yes, but technology is changing (mostly for the better) so you should
be prepared to change your code to keep up with this. Nothing stays
the same (except on Windows perhaps, but we see what this gets us -
inconsistent APIs and tons of outdated documentation).
MacOS X is a fundamentally new OS, with Carbon Apple did a great job
with at providing a way to migrate older code to a new OS but at some
point it makes sense to exploit what the new system has to offer. This
is inconvenient, but necessary, and requires a paradigm shift on our
part as well.
--th
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden