5 ms·
The pace of breaking changes is slowing down. Swift 3.1 was intended to be source compatible with 3.0, and Swift 4 has a "Swift 3.2" mode which tries to be sour
by slavapestov 9y ago
The pace of breaking changes is slowing down. Swift 3.1 was intended to be source compatible with 3.0, and Swift 4 has a "Swift 3.2" mode which tries to be source compatible with 3.0/3.1.
- jorgemf 9y agoSo, you agree with my comment? It still needs a bit more time to stabilize.
- kobeya 9y agoLanguage stability may not be a goal.
- jorgemf 9y agoThat is a problem for medium-big projects.
- valuearb 9y agoNot really. Xcode will automatically translate swift code to update it to a new version, and it has worked pretty well in most cases. The exception being the v2 to v3 transition, which was pretty onerous. My experience with some medium projects is that it costs me a morning every update. I'm okay with that because Swift is such a more productive and higher quality language than Objective C.
- jorgemf 9y agoSwift is not meant to target only Xcode. I am a Linux user and I would want to use swift for server development.
- M4v3R 9y agoIt seems it does, but they do put effort to make the transitions as easy as possible.