Kathy Walrath

Agreed. This is about https://www.dartlang.org/guides/language/language-tour, right? It predates DartPad (and, in fact, was published as a book first) but we should update everything to have a DartPad and, perhaps, use...

Current thinking is that making _everything_ a DartPad would be rather overwhelming, and that we should instead make the first one an embedded DartPad. After that, we'd use DartPads wherever...

I tried using a DartPad for the first example in the language tour, but unfortunately there's a lag when you first load the page. Bad experience. I'll leave this open,...

> That consistency and simplification sounds great to me! Function should be understood without even looking at the glossary in most cases, so that seems like a good direction. @kwalrath...

There's also the article [The Event Loop and Dart](https://webdev.dartlang.org/articles/performance/event-loop), which is currently on webdev but I think is applicable to Flutter. I agree we should think about this. How do...

And also [Futures and Error Handling](https://www.dartlang.org/guides/libraries/futures-error-handling), which somehow didn't make its way onto the list in #407. It's the 60th most viewed page on the site.

> Interim fix: add link from Andrew's event loop article to an archive URL like https://web.archive.org/web/20170704074724/https://webdev.dartlang.org/articles/performance/event-loop. DONE

I've just discovered an internal resource that seems helpful: go/dart-await. It refers to [this DartPad](https://dartpad.dartlang.org/12bf241722ad99087134e07e26bc0c7c) and [this article](https://www.woolha.com/articles/dart-event-loop-microtask-event-queue).

There's a new concurrency page, but it doesn't cover microtasks: https://dart.dev/guides/language/concurrency

We could really use a simpler example here. This one is rather hard to read, and it isn't tested. About the existing code: * I think arguments and argResults aren't...