Man I don't know why there is soo much hate towards v4... but I personally love it. I think it's one of the best IDE's available on any platform. Yes there are bugs... but there are bugs in every IDE. Go try and use Visual Studio. Gah.
To be honest, it seems that the majority of the noise is about a slightly different workflow than what is used to from v3. My answer to that is, adapt or di... err I mean, or get fired. My $0.02 anyway. -Gene On Thu, Mar 1, 2012 at 6:01 AM, George Toledo <gtole...@gmail.com> wrote: > I'm not sure how/why this has spilled over to the Cocoa list, but out of > curiosity Wade, did you work there after Xcode 4's release? If not, I think > the argument is slightly specious. > > Does anyone require devs at Apple to use Xcode 4, or conform to the broken > technologies that are foisted upon outside Developers? I don't know... > totally rhetorical, but I'd hope not, because as bad as it is to have this > put upon us, I'd hate to think they're using this trash across the board. > > -gt > > > Message: 4 > > Date: Wed, 29 Feb 2012 16:41:27 -0800 > > From: Wade Tregaskis <wadesli...@mac.com> > > To: Matt Neuburg <m...@tidbits.com> > > Cc: "cocoa-dev@lists.apple.com" <cocoa-dev@lists.apple.com>, Joar > > Wingfors <j...@joar.com> > > Subject: Re: Xcode - An Apple Embarrassment > > Message-ID: <f326e419-d299-4e21-aeb9-4748662ac...@mac.com> > > Content-Type: text/plain; CHARSET=US-ASCII > > > >> *No*. I've said it before (right here) and I'll say it again; this is > *not* jumping to the documentation, and it is *not* doing what Xcode 3 did. > It switches to the documentation window and it enters the double-clicked > word into the search field, and it does the search, but it ****doesn't > display the actual documentation**** on the double-clicked word. > > > > Indeed, the regressions around this simple piece of functionality are > disturbing. I also find that it rarely handles double clicks correctly. I > have to triple or quadruple-click much of the time. It's often faster to > just bring up the organiser (command-shift-2, obviously) and navigate to > the desired docs directly, than play some kind of bizarro skill game with > my mouse button. > > > >> Once again I put forward my pet wild-and-crazy "dog food" theory that > the people at Apple do not actually *use* Xcode for serious work. I know it > sounds wild and crazy, but I have two kinds of evidence for this theory: > > > > Occam's razor (and my own nearly four years working on developer tools > at Apple) will present a different explanation: Xcode is used exhaustively > within Apple, but the Xcode team just aren't good at producing a solid > product. I'm not sure why that is; all the people I know on the Xcode team > are very good developers, at least individually. > > > > Someone else pretty well hit the nail on the head earlier when they > suggested that developer tools just aren't given much top-level interest. > I don't know if that can be blamed for the end result though. > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > > https://lists.apple.com/mailman/options/cocoa-dev/emailgeneonthelist%40gmail.com > > This email sent to emailgeneonthel...@gmail.com > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
