News for hackers. Stuff that matters.
Re:Evolving the Dart Language with Dart Enhancement Proposals by bsaul on Thursday March 05, 2015 @10:49AM (#9151386)
It's funny, but now that i've used golang, i can't help that think that async/await or any concurrency primitive isn't the kind of thing you add to a language in an update, but rather the things you build the language around.

Edit : of course that comment applies to server-side oriented languages. For client-side code running in a browser, this is less of an issue. Actually, dart-to-js on the client + golang for the api could be a good combo...

Re:Evolving the Dart Language with Dart Enhancement Proposals by xxgreg on Friday March 06, 2015 @02:37AM (#9156019)
The team are also working on an experimental VM with support for coroutines and channels, threads will also have growable stacks, that will allow a similar programming style as used in go. See: https://github.com/dart-lang/fletch

Async/await is just sugar, it doesn't actually change APIs at all. Note C# also added async/await long after their first release.

Re:Evolving the Dart Language with Dart Enhancement Proposals by sethladd on Thursday March 05, 2015 @12:51PM (#9152454)
Dart had Futures and Streams (the underlying classes for async) built-in from day one, and Dart has always been an event-loop-per-isolate language. The async/await/etc language features just make asynchronous programming much easier.