Looking back on Swift 3 and ahead to Swift 4

&gt; - First class concurrency: Actors, async&#x2F;await, atomicity, memory model, and related topics. This area is highly desired by everyone, as it will open the door for all sorts of new things on the client, server and more. We plan to start formal <i>discussions</i> about this in Phase 2, but it is unfortunately crystal clear that a new concurrency model won’t be done in time for the Swift 4 release. This is simply because it will take more than a 12 months to design and build, and we want to make sure to take time to do it right. It also makes sense for the memory ownership model to be better understood before taking this on.<p>It&#x27;s great to hear planning and discussion on this is beginning, and that they&#x27;re being honest upfront about the timeline to see it implemented.

I&#x27;m very happy that Apple open sourced Swift.<p>Chris and his crew are amazing and the vibrant community definitely helps&#x2F;challenge them and will bring us things like:<p><pre><code> - concurrency (at least planned) - cyclone&#x2F;rust memory model! - scripting - syntactic sugras </code></pre> Congrats!

Wow quite intriguing and exciting that swift 4 may have a rust inspired memory model!<p>Can definitely see the use case for swift expand a bit with this in its wings.

Awesome things in store for Swift. With Rust like memory model as alternative and async&#x2F;await I think it will massively broaden the appeal of Swift. I can start to see Swift taking over as the main mainstream language in the future. Java and C# has just accumulated too much cruft, they will be the new C++ languages. You can do anything but you have to accept a lot of complexity and awkward syntax to do that.

Perhaps, one should borrow message-passing as a standard language idiom, actors and pattern matching on receive from Erlang, the way Akka did, instead of copying hat async&#x2F;await ugly hacks.<p>Message passing as a core concept of a language is fundamental and necessary (given that interlop with ObjC is important), and having that and macros gives related control structures for free.

Wouldn&#x27;t First class concurrency in a way breaks ABI and Stdlib as well? ( Otherwise it would be second class )

<p><pre><code> &gt; For Swift 4, the primary goals are to deliver on the &gt; promise of source stability from 3.0 on, and to provide &gt; ABI stability for the standard library. </code></pre> Hm, does this imply that only the stdlib will have the benefit of a stable ABI? IOW, that it won&#x27;t be possible to distribute compiled artifacts built with different versions of the compiler and expect them to link properly?

I just run Ubuntu now but I like the features of Swift.<p>Does anyone who uses Swift on Linux have any comments, suggestions, use cases, etc.?

The question I still have, is when will Swift 3.0 release be available in Xcode and for Linux use? The comment of Swift 3.X release in spring 2017 can&#x27;t be 3.0, or am I missing something?

is offical Windows support planned?

Why does mailing list archival software not contain basic css? Long lines make it hard to read the text.<p>You don&#x27;t even need much css: <a href="http:&#x2F;&#x2F;bettermotherfuckingwebsite.com" rel="nofollow">http:&#x2F;&#x2F;bettermotherfuckingwebsite.com</a>

Kind of an incomplete article as there is no mention of the environmental cost. Desalination is not a magic solution. Everything is a trade off. Desalination means pumping salt back into the ocean which just compounds the problem.