On Mar 25, 2015, at 07:38 , Michael Domino <[email protected]> wrote: > > On 10.10 we’ve been seeing a lot of random crashing.
> … move to Xcode 6.2 on 10.10 … which I would like to do, but I need some good > reasons for doing so. You just said a really good reason for doing so. If crashing has “started” on 10.10, that just means you’ve been unfortunately lucky prior to 10.10. (Unlike in the real world, the failure of bugs to show up is bad luck that you wish you didn’t have, not good luck.) In a situation like this, where you have others holding you back, I’d suggest you simply propose taking 2-3 days to *try* switching a copy of the project to Xcode 6.2. If it goes well, all and good. If it turns into app redesign hell, just continue with the original project and Xcode 3. It’s hard to predict, but the outcome is probably one of the extremes (it takes a couple of hours vs. it’s going to take weeks), and a day or two spent on finding out is not wasted. The most significant negative indicator is garbage collection. If your app uses it, there’s a good chance that a major** app redesign is needed, because you’ll have to devise strategies for preventing unwanted reference cycles in ARC. Also, depending on the way the app is deployed, it’s not ridiculous to split the app permanently, with one version for 10.5+, and a new version for 10.10 (or 10.9-10.10 or even 10.8-10.10, depending on which SDK you want to use). That leaves the old version to fade gracefully away over time. FWIW. ** “Major” not so much in the sense of much code rewritten, but rather that very fundamental assumptions may have to be revised, causing outward spreading ripples.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
