Thank you Chris for the detailed explanation.
The only passage that really worries me is:
>The problem is not staffing levels or competence/expertise, it's just
>that there's an awful lot of work to do. Mac OS X is much larger
>(orders of magnitude so) and moving much faster than Mac OS 7/8/9. It
>took eight years to go from System 7 to 9.2.2. Mac OS X has been out
>for only 5 1/2 years and has released five major versions, with a
>sixth already in Developer Preview.
Sure enough, that is something beyond the Xcode team's responsibility. I
do feel that Mac OS X is moving too fast, if only as a sign I have some
rather basic radar bugs filed on things that worked nicely in 10.3, but
got (and still are) broken in 10.4 after over a year after having
reported them (e.g. 4219620, 4422688, 4221599, 4365051). To an external,
this creates the impression that resource allocation is favoring the
"bleeding edge front" compared to the "first let's make the things we
already have actually work" side.
I really, really hope OS X does not eventually get bitten badly by
moving that fast, neglecting thorough bug-fixing and refinement of the
existing features on its way.
So yes, I do understand the huge challenges the Xcode team is facing.
Regards, Christian.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
