“This time last year iOS developers across the globe had no idea that in a few days Apple would launch a brand new programming language called Swift at their Worldwide Developer Conference,” Charley Allen writes for Amsys. “We were streaming the WWDC keynote live in London when Apple announced the arrival of Swift. I remember looking over at Richard, our Head of App Dev and creator of Amsys iOS Development training, with his jaw on the floor.”
“From our experience, Swift is easier to pick up than other languages, and if you come from another language you will certainly find it very familiar. Once you get into the iOS or OS X frameworks, the building blocks of any app, you will notice they are identical in functionality, they just differ in their syntax,” Allen writes. “If you’re coming from Objective-C to Swift, you should feel right at home.”
Read more in the full article here.
MacDailyNews Note: The Swift Programming Language, a free 500-page manual from Apple, is available via iBooks Store here.
SEE ALSO:
Swift performance in Apple’s Xcode 6.3 beta – February 18, 2015
Longtime NeXT/Apple developer exalts Swift 1.2 – February 10, 2015
Apple’s new Swift programming language takes flight – February 7, 2015
So…the IBM post was not your last post? LOL.
Maybe it’s about time to take a look again.
Still, I’m not excited about a language that doesn’t support exception handling. Also, the last time I seriously looked at it (4-6 months ago) the string library was pathetic; that, however, is something that can be fixed (unlike exception handling which is an anathema to the Swift language designers).
At least they have fixed the *major* compile time issues with the compiler (and incremental builds). Last time I looked Swift was not ready for prime-time; that may have changed in the past six months.
i read somewhere they didn’t include exception handling because so many people misuse it in other languages. that’t why we can’t have nice things!
That’s exactly why they left it out and they said so. Exception handling was designed for lazy programmers. Do all your own damned checks before you do something.
More like, the design philosophy of Swift is that it’s better if you don’t have to throw any exceptions in the first place. That’s why its so strict about type safety and never allowing the use of uninitialized memory.
-jcr
also, any language like c++ that needs an entire book with a trout on the cover to explain the byzantine convoluted strings library doesn’t get any gold stars either.
Just PLEASE Apple: Don’t even remotely compromise the memory management manifesto of Swift. If you can hold that line and kill off buffer overruns, ooo baby! That’s a killer programing language!
Apple’s first iteration of Swift was so bad that the language syntax did not match the information in their own Swift book. The syntax for looping over closed intervals comes to mind. I would like to say that Swift has gotten much better. As a former Visual Basic user, I like swift better because I like Apple’s GUI building system better than .NET’s. Cocoa whether you use Swift or Obj C remind me a lot of Delphi and C++ Builder ( the last thing Borland did correctly).