51–60 of 159 posts
Ted Kremenek doesn't seem to be a very active contributor of Swift. https://github.com/tkremenek https://github.com/apple/swift/graphs/contributors
And yet Chris still thought he was fit to lead the group. Maybe in a project leadership role it's not all about how many commits you make?
Lots of great people leaving Apple right now, not a good sign.
I don't use or follow Swift, but Chris was also instrumental in the development of LLVM, which has become hugely important in all sorts of areas. Has he still been active in that while working on Swifty stuff, or have other people taken over there already?
I 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.
Did you read the email at all? 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.
>Please don't insinuate that someone hasn't read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that."
Not nitpicking, but we can miss things or we can be looking at different things.
Case in point, one time on a Python mailing list, I asked a question and one person pasted something from the docs. I had read the docs for what I was trying to do before asking the question, specifically the paragraph pasted and I just thought "How could I have missed that?". It turned out they were pasting the docs from Python 3 and I was reading the docs for Python 2.7. The paragraph was identical in every respect, except for the particular thing I was talking about which was changed with Python 3.
Swift 4? Wow, they surely are iterating quick... How's the backwards compatibility in Swift between major versions? If I understood correctly, Swift 3 was supposed to be the first production-ready release. Or am I wrong?
Swift 4? Wow, they surely are iterating quick... How's the backwards compatibility in Swift between major versions? If I understood correctly, Swift 3 was supposed to be the first production-ready release. Or am I wrong?
Welp... 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…
So... are you down voting my comment because you don't consider it a quality comment, or do you just not like what I have to say?
(I didn't up or down vote, I'm just echoing how it reads to me)
Edit: Had your original comment included that extra backstory/justification, it surely wouldn't have been hammered with downvotes. Without it, it just reads like snark.
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.
> I really didn't want to go back rewriting code every year. The changes are mostly syntactic and like API changes. And Xcode has an integrated migration tool that's not too bad. I ported approx. 23KLOC of Swift ( http://audiokit.io ) from 2 to 3 in like 3 hours. And the changes are generally for the better.