On Fri, 12 Jun 2015 23:51:42 -0700, Britt Durbrow said: >Swift is too immature to warrant doing anything serious with it yet…
I've stayed away from it for that reason basically. When Xcode x+1 can't even compile code that builds in Xcode x, I'm not too interested (except for toy projects). Yeah, I know there's a code migrator, but then god help you if Xcode x.y+1 has some regression and you need to go back to x.y, which has happened to me more times than I care to count. Some stability in the language is needed before I use it for big/serious projects. >Personally, if I had the time to dedicate to it, I’d come up with some >non-critical project (i.e, something not “serious”, but big enough to >qualify as “non-trivial") to do in Swift for the purpose of developing >that skill set. Exactly. In my case, the new automated UI testing in Xcode 7 looks like the perfect opportunity to write some initial Swift code. The open sourcing of Swift is also vital. I wouldn't use it otherwise. There are just too many great tools in the llvm ecosystem that would be excluded otherwise. Things like clang-format, address sanitizer, etc that all support Obj-C thanks to it being in clang (otherwise those tools would only support C/C++ I'm sure). Cheers, -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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
