![swift-language-logo[1].jpg](https://i.imgur.com/5RDViMV.jpg "swift-language-logo[1].jpg")
Is Swift the future?
It's the future android needs but not the one it deserves
Why would it?
>>54909194
R U BATMAN?
>>54909194
How long until Android switched to Swift?
Someone redpill me on Swift, i barely come to this board
>inb4 google
I want the /g/'s opinion
yes. it's done a good job at making a language with a decent type system available to the masses, which hopefully means better software. also it's a lot less verbose than shit languages like Java so hopefully people will realize that designated languages suck dick when they see how much nicer it is to develop for iOS vs. Android. at that point, jewgle might drop Java and either switch to Swift or use a different language with similar properties (which is a good thing if you don't like shitty designated apps on your phone, plus Java performance is garbage and a nicer language could take better advantage of your phone's hardware).
that said, it's still suffering from Apple's shitty politics/hipster bullshit because they have this insane fear of having features, and rather than standing by their old decisions they decide to remove them in each new version. not only are they constantly breaking compatibility, but they also consistently remove the better of 2 options because retards prefer the worse one over the better: for example, rather than keeping functions that only take one argument (allowing more through tuples or currying), they switch to multiple arguments (which makes it significantly harder to reason about functions and write very generic higher order functions). the only reason they really did this is because "it's too hard" for normies to do, but with the change they lost a lot of expressiveness.
>>54909410
As soon as Apple quits using Blackberry's QNX for their Apple Car systems :^)
>>54909640
I understand the urge to have currying in the language but removing it made sense, it added unneeded complexity to the language. The way swift is going is making me personally very confident in its future. The proposals accepted for Swift 3.0 are looking really good.
Swift is definitely the future for Apple development, I'd love for it to become commonplace in teaching.
>>54910998
Now if only it wasn't just exclusive to iOS/OSX/tvOS/watchOS
In all likelyhood, go is far more likely to be the future, not swift. No fucking clue which is even better, but go has way more momentum behind it than swift.
>>54911016
Foundation is open source.
Apple provides builds for Linux (Ubuntu).
I don't really understand?
>>54911050
I can imagine Google having a change of heart in a year or two, and killing it, just like they kill everything else.
>>54911133
I mean it seems like it's only used to build iOS apps and such.
>>54909069
Are you asking a question that only a shill would know the answer to?
>>54911153
There's a difference between what the language is used for and what it can be used for.
Apple provides the best tools for Swift at the moment, and Apple's dev tools are for its own platforms.
>>54909410
>>54909640
Think kotlin might end up somewhere?
https://kotlinlang.org/
Seems to be interoperable and has null checks and some other things built in.
>3 major versions
>STILL no stable ABI
>STILL introducing source-breaking changes
iCoders are like battered wives
language is too janky. scala is the future
No.
