3 ms·
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 i
by bsaul 12y ago
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...
- sethladd 12y agoDart 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.
- xxgreg 12y agoThe 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 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.