Swift 3.0 Released
swift.org
Swift 3.0 Released
1–10 of 95 posts
Re: Swift 3.0 Released
#2> It is not source-compatible with Swift 2.2 and 2.3.
This created havoc in Python. Hopefully it won't happen here.
Re: Swift 3.0 Released
#3> It is not source-compatible with Swift 2.2 and 2.3. This created havoc in Python. Hopefully it won't happen here.
Until now Swift has not promised source compatibility so the developers should be ready to rewrite their code for new versions. I would not be surprised if Swift 2.3 support were dropped in the next version of XCode completely.
The migration tools are quite good though so going from 2.2 to 3.0 directly should not be much of a problem.
I think that in Python the problem was/is that the 2.x was already a massively used and mature language when the 3 came out.
Re: Swift 3.0 Released
#4> It is not source-compatible with Swift 2.2 and 2.3. This created havoc in Python. Hopefully it won't happen here.
As per the blog [0], you can expect a lot to break.
Swift 3 is a source-breaking release, largely due to the
changes in SE-0005 and SE-0006. These changes not only impact
the names of the Standard Library APIs, but also completely
change how Objective-C APIs (particularly from Cocoa) import
into Swift. Many of the changes are largely mechanical, but
they can be numerous in a typical Swift project.
To help with moving to Swift 3, Xcode 8.0 contains a code
migrator that can automatically handle many of the need source
changes. There is also a migration guide available to guide you
through many of the changes — especially through the ones that
are less mechanical and require more direct scrutiny.
Re: Swift 3.0 Released
#5congrats!
Re: Swift 3.0 Released
#6> It is not source-compatible with Swift 2.2 and 2.3. This created havoc in Python. Hopefully it won't happen here.
It makes a lot of sense, though. Like many new languages Swift was invented hastily and without much care with the main goal of locking in developers and preventing cross-platform development. If Apple made major releases backwards-compatible, this would invariably turn the language into a big mess in the long run.
This way, the language can evolve into a fine language with many features from Algol-68 and the usual semi-popular C-ish syntax, and Apple can continue to ensure that developers have to maintain a separate codebase for their "apps" that is useless anywhere else.
Re: Swift 3.0 Released
#7> It is not source-compatible with Swift 2.2 and 2.3. This created havoc in Python. Hopefully it won't happen here.
It makes a lot of sense, though. Like many new languages Swift was invented hastily and without much care with the main goal of locking in developers and preventing cross-platform development. If Apple made major releases backwards-compatible, this would invariably turn the language into a big mess in the long run. This way, the language can evolve into a fine language with many features from Algol-68 and the usual s…
>Swift was invented hastily and without much care
Swift was started in July 2010 by Chris Lattner[1] and it was publicly announced by Apple in June 2014 (and the 1.0 release was September 2014). Spending 4 years on it and including other programming language experts to contribute to it doesn't seem like a reckless and thoughtless release. What it shows is that even if a group spends years on it, they will still get a lot of things wrong. Same for C# that was (formally) started in January 1999 and not publicly released until December 2002. Even though that language also had 4 years of gestation by smart people, they still got generics and a bunch of other things wrong (e.g. terrible name of "destructors" for the concept of finalizers.)
I didn't realize that programmers thought Swift was created in a hurry like Brendan Eich's "10 days" to design Livescript/Javascript for Netscape Navigator[2]
[1]http://www.nondot.org/sabre/
[2]https://www.quora.com/In-which-10-days-of-May-did-Brendan-Ei...
Re: Swift 3.0 Released
#8> It is not source-compatible with Swift 2.2 and 2.3. This created havoc in Python. Hopefully it won't happen here.
Almost every version of Swift until now has had source-breaking changes. We're used to fixing things every 6 months or so.
Re: Swift 3.0 Released
#9> It is not source-compatible with Swift 2.2 and 2.3. This created havoc in Python. Hopefully it won't happen here.
Until now Swift has not promised source compatibility so the developers should be ready to rewrite their code for new versions. I would not be surprised if Swift 2.3 support were dropped in the next version of XCode completely. The migration tools are quite good though so going from 2.2 to 3.0 directly should not be much of a problem. I think that in Python the problem was/is that the 2.x was already a massively used…
The conversion tools failed pretty badly in my case. I had to do a ton of manual fixes. There are also still a lot of libraries out there that haven't updated yet so unfortunately I'm holding off on updating for now.
Re: Swift 3.0 Released
#10> It is not source-compatible with Swift 2.2 and 2.3. This created havoc in Python. Hopefully it won't happen here.
It has also created havoc in the Swift world. Suddenly all existing Swift code is broken. The migration tool is supposed to take care of most of this for you but my experience has been that it misses a lot of things and upgrading requires many manual fixes. Of course every Swift library in existence also needs to be updated so your changes of a smooth migration right now are slim.
Apple has the resources to push this through and developers don't really have much choice so I don't expect this to become another Python 3 fiasco but this really should be the last time Apple breaks so much code just to clean up the syntax a bit.