> On Apr 6, 2016, at 8:04 PM, Luther Baker <lutherba...@gmail.com> wrote: > > I have no idea what I'm talking about but I sort of wish the IDE tooling were > more separated from the SDK. It seems odd that one has to keep upgrading the > operating system and IDE to use the newer iOS SDKs.
I agree, and I suspect the Xcode team agrees too, but there are probably hidden complications that would make it hard to split them up (as they used to be, when there was a separate /Developer folder.) I can imagine there would be all sorts of conflicts where version A of the SDK wouldn’t work with version B of Xcode because of some new compiler feature or language syntax change or something… > Swift is in such flux right now. Surprised to see operator++ was deprecated. > Paradigm shifts and obvious changes aside - for me, that change alone > signifies a real changing of the guard. Yeah, it’s a bit of a bumpy ride using Swift, but I’m impressed at how committed they are to doing the hard work of making the language cleaner. (And the process is all very open; if you follow the Swift mailing lists you can see the individual proposals and debate them and even propose your own. IIRC the “++” deprecation was suggested by people outside the Swift core team.) It helps that they have a secret weapon in Xcode’s “fix-it” feature. It’s a lot more feasible to change the language syntax when the IDE can upgrade everyone's source code semi-automatically. —Jens _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
