Flutter: a Portable UI Framework for Mobile, Web, Embedded, and Desktop
It feels wrong architecturally for Google to be pushing this right now:<p>1) Dart was intended as a Java like language and is inferior to Kotlin, a language they just endorsed on Android yesterday. Dart feels like a step back, not forward. The message is confusing from Google on this front. They have a huge Kotlin developer community already. Why push Dart at all?<p>2) World + dog is moving towards compiling Kotlin and many other languages to web assembly as well as native. Cross compiling Dart to javascript was maybe a valid choice a few years ago but not in 2019. See e.g. Rust roadmap for this year, .Net 5.0 agenda for MS, Kotlin Native, etc.<p>3) LLVM seems to be the toolchain of choice for this type of stuff to happen. Go and Kotlin + WASM would be very valid choices for Google to prioritize on this platform.<p>4) In a browser you need to be driving the DOM to look and feel like a proper web application. If you abandon that notion, you might as well grab something like QT or some other UI toolkit and use that.<p>My recommendation would be for Google to untangle flutter from Dart and just retire that and focus on WASM and native based runtimes only. That&#x27;s going to take time and in my view it&#x27;s inevitable that whatever they are pushing right now is ultimately going to be deprecated in favor of something like that.