Earlier quoted context omitted.
Just curious, why do you say that (about Go)?
It feels much too pragmatic for my taste. Exactly the kind of thing to come out of Google, to solve their type of problem (scalability, deployment are much more important than the code itself). Personally I don't have googles problems (few of us do!) and I really like a good type system, with algebraic types/pattern matching/generics
“Swift will be open source later this year”
321–330 of 573 posts
Re: “Swift will be open source later this year”
#322Re: “Swift will be open source later this year”
#323Well whaddaya know, I like the direction this is going with both Apple and Microsoft.
I'll second that when Apple and MS will support Vulkan on their OSes and open codecs in their browsers. Or to put it another way, when they'll stop using sickening lock-in to make life harder for everyone.
Re: “Swift will be open source later this year”
#324Well whaddaya know, I like the direction this is going with both Apple and Microsoft.
I'll second that when Apple and MS will support Vulkan on their OSes and open codecs in their browsers. Or to put it another way, when they'll stop using sickening lock-in to make life harder for everyone.
Re: “Swift will be open source later this year”
#325> Swift will be open source later this year, available for iOS, OS X, and Linux. They're doing Linux but not Windows? Is Windows not sufficiently important or maybe they just forgot to include Windows in the announcement?
Re: “Swift will be open source later this year”
#326Earlier quoted context omitted.
Open Source did not win. In fact it destroyed a lot of potential markets. With this move Apple is dragging more and more developers that would be interested in Go/ Java (aka Android world) to its net. This is a win for Apple only.
Part of me says that any ecosystem that can be 'destroyed' by something as simple as near-zero-cost copying of product should never really have been a 'market' to begin with. We don't hear a lot about the sunshine or oxygen markets.
Re: “Swift will be open source later this year”
#327Hmm they said they wanted Swift used everywhere for the next 20 years, they're going to make it open sourced and provide builds for iOS, Mac and Linux...but not Windows which is one of the largest operating systems in the world? I'm guessing they really don't want it used everywhere. Though knowing Microsoft they'll take Swift and implement support for it in Visual Studio.
Re: “Swift will be open source later this year”
#328Apple explicitly said they see Swift as a systems language... curious what people thing about that. Does it compete with C/Rust, or is it just a pipe dream/marketing message?
It's designed to give it hype, it's not a systems language. The first question you should ask for any systems language is how to I integrate assembler, when the answer is to use C / C++ then you know it's not a systems language. Also, how you can tell a language is a systems language, it has an operating system written in it used by a large user base. How do you layout a struct in Swift so that it's the exact size an…
Edit: You can also link against .o files with Swift, which is the only sane way to integrate assembly language anyway (i.e. in a separate compilation unit).
Re: “Swift will be open source later this year”
#329Can someone explain what it means for a language like this to be open source? I sort of get it for Python, means you can download the C files and mess with them. But isn't Swift written in like Assembly?
It's potentially great news. It means I potentially don't need to own a Macbook Pro and use XCode just to build apps for iOS. Fuck that shit.
Re: “Swift will be open source later this year”
#330Earlier quoted context omitted.
I think the "pulling it off" here is coercing their megacorp organization into tolerating the idea of open-sourcing something they poured so much time and money into developing. This is also why people have been celebrating Microsoft open sourcing things recently.
"By the end of the year" perhaps suggests that Microsoft got out in front and Apple's hand has been forced into changing their roadmap. I suspect that Apple will struggle with to support cross platform development beyond tossing Swift over the transom. Supporting diverse execution environments is not their core competence historically.