Flutter: Futures, Isolates, Event Loop
didierboelens.com
didierboelens.com
By comparison, Grand central dispatch is pretty nice on iOS, but I really miss the first class async/await calls. Side note: How did they make an entirely new language for app development (Swift) and not build in async/await support?
Kotlin co-routines seem to be a pretty nice solution on Android, but before that it was a bit of a mess. There was 4 or 5 different ways to do things async, they all interact in super complicated ways with the activity life cycle, and basically nothing is quite what you need.
Side side note: Unity also does a really nice version of all of this with a single event loop and really powerful co-routines. Worth checking out sometime.
Because whether a language is slow to evolve only makes sense relatively to some baseline rate.
>Technology and it's pace isn't the same as it was decades ago, and I see no reason that we should hold it to the standard of that time.
And yet still, today, popular languages take their time to get features like async/await. Python got it after 3.6 (so 20+ years on), JS only got it in 2017, C++ doesn't have it, Rust doesn't yet have it (it's coming), Java doesn't have it, C++ doesn't have it...
Heck, Golang doesn't have generics and comfortable error checking still...
In my experience, Swift is lacking any particular major improvement over ObjC. It seems like async/await could have been that big step, and Swift probably shouldn't have been adopted until it was in place. Just wasn't worth it.
I realize that's a controversial topic and I know people who love Swift, just from my perspective it was such an enormous cost without enough upsides to justify it.
There are some interesting things that Unity coroutines do, like the idea that routines are tied to owners that are running them, so when the owner's life cycle ends, the coroutines no longer continue. However, as a whole I think there's a lot wrong with them. They're not any safer than Android's async functionality, they just make doing anything off the main thread almost impossible so threading issues are easier to deal with. The whole wait and continue functionality of them is also very frustrating in implementation with many exceptions and hacks.
By building it gradually and not rushing everything from the first day.
That said:
https://gist.github.com/lattner/429b9070918248274f25b714dcfc...
https://gist.github.com/lattner/31ed37682ef1576b16bca1432ea9...
I must say wrapping my head around the addition of 'await' and the changes it made to the EventLoop processing was difficult but as I type this comment I realize I do fully grok it now. I must say that this is IMO probably the most important piece of info in the article.
Basically,
"`await` causes immediate execution of the Future (up to the first `await` in the Future) verses appending the Future to the end of the EventLoop queue"
If I have the above wrong someone please call me out.
Great article.
It looks like the Dart concurrency model is basically the same as JS except with microtasks and replacing “worker” with “isolate.”
In the first example `await` is added before the Future creation and this causes immediate execution in the printed output (second version). In the first version both Futures are pushed onto the EventTask queue and are executed after main() has finished.
In the second example with method1 and method2, in method1 with async (which signals a Future) on the forEach, all three Futures are pushed to the EventLoop queue and execute after method1() has finished. In method2() there is no new Future being added and execution happens immediately with the end of method2 executing after all delayedPrints.
You also see the effect with all three Futures resolving at once in the method1 case due to all three being added to the queue at the same time each with the same delay. Whereas with method2 each print with a delay after due to this function being synchronous with nothing going on the EventLoop.
The code example where D doesn't get called last because of the missing await grinds my gears something fierce, especially because I missed it the first glance through. This type of bug is much harder to create when you don't constantly rely on side effects everywhere.
That said, the article did a really good job if you're not already familiar with the same concepts from JS land (with the event loop sans visible microtasks, Promise instead of Future, abd web worker instead of Isolate).
For the Dart part the Future-problems you already mentioned and the need for async/await language level keywords is disappointing. Also if/else not being an expression as well as syntactic complexity (e.g. defining constructors with factory/static/const keyword combinations). Why come up with a new language in 2011 that repeats the null mistake?
Flutter gives you a beautiful and comprehensive set of widgets and makes a great first impression. But when digging a bit deeper, things tend to get ugly. Massive side effects hidden deep inside OOP structures (e.g. routing), stuff like mixins, validation tied into view layer etc. I couldn't help but find so many mistakes being repeated.
After spending a couple months with Flutter, I decided to ditch mobile development all together. I wish they followed the direction react is steadily going: promoting simple, pure widgets and passing values around, avoiding side effects.
This is unfortunate [1], I agree. The challenge is that if you don't do that, it's very hard to compile the resulting code to efficient JavaScript. Dart was initially only a web language and is now both a web and a mobile language.
You can think of function calls as having two different calling conventions: return the value normally, or return it by invoking a continuation with the result. Asynchronous functions require the latter. You could compile all function calls to that style, but it's much slower and generates larger JS.
You could try to infer which functions should be called using an async style and which shouldn't. That works in simple cases, but breaks down in complex cases involving generics and higher-order functions. I don't know of any literature that investigates how feasible this is in practice, so making your language rely on this optimization for tolerable performance is a very large gamble.
This may change over time now that JS has generators and may be adding async/await syntax, but Dart was designed before either of those existed.
> Also if/else not being an expression
Yeah, everything being an expression is nice. I wish Dart had been designed that way. The original designers of the language believed they needed to be very conservative in order to be successful and I think they overshot that mark.
> syntactic complexity (e.g. defining constructors with factory/static/const keyword combinations)
Some of this is annoying, yes. It does have some practical value, though:
* The restriction around initializing final fields in the constructor initialization list, which is what forces you to use factory constructors in some cases, ensures a very nice property: it means in Dart you can never observe a final field before it has been initialized. This is not true in C#, Java, or Kotlin. Now that we are working on non-nullable types for Dart [2], this will let us have sound non-nullable types, unlike those other languages.
* Personally, I find const to be more of a hassle than it's worth, but const constructors do let you define real compile-time constant objects of user-defined classes, which isn't something some other languages can express. That, in turn, lets you rely on very fast identity tests for checking equality between two objects. Flutter relies on this heavily when diffing the widget tree to determine which parts have changed efficiently.
> Why come up with a new language in 2011 that repeats the null mistake?
Tell me about it [3]. (Note the date on that blog post.) We're working to fix it now.
[1]: http://journal.stuffwithstuff.com/2015/02/01/what-color-is-y...
[2]: https://github.com/dart-lang/language/issues/110
[3]: http://journal.stuffwithstuff.com/2011/10/29/a-proposal-for-...
> the outcome of the method is a Future
Isn't the function signature sufficient to express this?
> it runs synchronously the code of that method up to the very first await keyword
How is this different from non-async methods?
> the next line of code will be run as soon as the Future, referenced by the await keyword, will have completed
But the await keyword is in the caller which is not statically known.
What is the difference between an async method and a method that returns a Future?
There's no difference for callers of the method, but you can only use await in methods that are async.
For example:
return 4;
If you allow a non-async method use await, you get into this situation:
Future<int> foo(){
int result = await something ();
// How to return "result" and still make compiler happy?
}It sounds like the async keyword allows for a particular implicit type conversion within the function body, but on return statements only. That's a pretty thin justification for a keyword.
If you don't uses async you have to do compiler's job yourself.
Future<int> foo() {
return Future.delayed(Duration(seconds: 1)).then((x) => 1);
}
I found a link [1] that described async as a compatibility affordance in C# 5: legacy code may use await as a variable name, so async opts into the contextual await keyword. But Dart doesn't have such legacy, so the keyword doesn't seem as well motivated.
https://blogs.msdn.microsoft.com/ericlippert/2010/11/11/asyn...
while (microTaskQueue.isNotEmpty){
...
return;
}
Isolate == Worker Future == Promise
But it probably also helps that one of dart's creators, Lars Bak also developed the V8 JavaScript engine.
Something to try to wrap my head around later!