I'm wondering if this means that the major work on Swift the language is complete? I've avoided it since it seems every year the language or the API changes... has it now settled? I really didn't want to go back rewriting code every year.
If you're truly worried, I would hold off just a little bit longer. Swift ABI stability is slated for Swift 4.
Update on the Swift Project Lead
41–50 of 159 posts
Re: Update on the Swift Project Lead
#42Re: Update on the Swift Project Lead
#43Let's start speculating what he might do instead. I have a hunch that this might pursue some Bret Victor-esque product maybe something like Swift Playgrounds for the iPad but less educational and more dev oriented. But I'm basing that on relatively nothing.
I hear he is going to work at an incubator started by the guy who sold the airline booking aggregator Aviato to a major airline in 2008. ;-)
Re: Update on the Swift Project Lead
#44I didn't see that coming, very disappointing news. Definitely a loss for Apple and Swift. I really hope he will somehow stay involved with the project.
This decision wasn't made lightly, and I want you all to know that I’m still completely committed to Swift. I plan to remain an active member of the Swift Core Team, as well as a contributor to the swift-evolution mailing list.
Re: Update on the Swift Project Lead
#45I'm wondering if this means that the major work on Swift the language is complete? I've avoided it since it seems every year the language or the API changes... has it now settled? I really didn't want to go back rewriting code every year.
Swift 4 will be ABI stable, i.e. you will be able to use Swift 4 binaries with Swift 5. So, starting in September things will really settle down, or at least, upgrades are not a problem anymore. I guess that XCode will stay compatible with Swift 4+ for a long time in the future, and it might even mean that changes in Swift 5+ will only be additions, like blocks in Obj-C were. UPDATE: Another comment here says that co…
Re: Update on the Swift Project Lead
#46Edit: perhaps the problem is that you assume I'm just tossing gasoline on the ever-loved and popular rag-on-Apple fire. I have been an active clang/llvm user for 6 years, I have written numerous clang plugins over the years, and I am an active swift developer. Every device I own is made by Apple and has been since 2004. I am genuinely puzzled why this comment is so unpopular (at least, considerably more so than goofy unfounded speculations about what Chris will do next—see above).
Re: Update on the Swift Project Lead
#47Re: Update on the Swift Project Lead
#48Earlier quoted context omitted.
Swift 4 will be ABI stable, i.e. you will be able to use Swift 4 binaries with Swift 5. So, starting in September things will really settle down, or at least, upgrades are not a problem anymore. I guess that XCode will stay compatible with Swift 4+ for a long time in the future, and it might even mean that changes in Swift 5+ will only be additions, like blocks in Obj-C were. UPDATE: Another comment here says that co…
Swift 3 code will be able to be used alongside Swift 4 code, in the future, but that's not to say that Swift 4 won't contain any breaking changes (it will).
Re: Update on the Swift Project Lead
#49I wonder who will take over managing Xcode and the other tools now, which was his other role.
Re: Update on the Swift Project Lead
#50Welp... there goes the last of the innovators I admired/followed at Apple. Edit: perhaps the problem is that you assume I'm just tossing gasoline on the ever-loved and popular rag-on-Apple fire. I have been an active clang/llvm user for 6 years, I have written numerous clang plugins over the years, and I am an active swift developer. Every device I own is made by Apple and has been since 2004. I am genuinely puzzled…