On 13 Jun 2015, at 16:42, Carl Hoefs <newsli...@autonomy.caltech.edu> wrote: > Bingo. Even after reading all the posts in this thread, I still don’t know > what problem Swift addresses, and no one seems to be able to answer that > question — not even Apple in its marketing hype.
I’m criminally simplifying here, but effectively, Swift means that someone ran C++, ObjC and Haskell into each other and removed all the C parts that cause problems for the optimizer. Which makes it a very solid foundation because you can use Swift to write code with C++-level compile-time checks and performance, against the native ObjC system frameworks Apple currently has, all the while becoming familiar with all the novel functional programming stuff Haskell offers. Now, the C++-level performance isn’t there *yet*, but that’s just because the people working on Swift haven’t gotten around to that yet. They’ve already eliminated the things that make the donating languages hard to optimize, so the foundation (lowercase) is there. If you’re not aware of how different Swift is from ObjC under the hood, I recommend you check out Jay Freeman’s talk from last year’s AltConf: https://www.youtube.com/watch?v=Ii-02vhsdVk Cheers, -- Uli Kusterer “The Witnesses of TeachText are everywhere...” http://zathras.de _______________________________________________ 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
