> Dart Server is not going to see a major uptick until Google commits to a major project initiative like they're doing with Flutter & Angular Dart. That's one

> Dart Server is not going to see a major uptick until Google commits to a major project initiative like they're doing with Flutter & Angular Dart. That's one of the important points for me. Google's commitment to Dart is... well.. Google-ish. The original intention as an alternative browser VM is done, most of the founding team left, and for years only the Google Ads team kept it alive. The Flutter "happened" and Dart had its "Ruby on Rails" moment. Now it seems tied to Fuchsia, too. A popular Non-google project would seem good, otherwise the comparison to Swift seems more appropriate than Go. With WASM being the new hot thing, I fully expect something Blazor-Ish to become quite popular in the Go world, and to be honest, once compiler output is going down, it's not that hard: the frontend stack is embarassingly shallow. I actually liked what I saw of Dart and like Bob Nystrom's way of communicating (he responds, but isn't all out evangelizing like e.g. some people representing projects that start with "R"). So don't get me wrong, it's great to see some enthusiasm, and it actually brought me back to fiddle around with it a bit over the holidays. But I still believe that's more my "I liked my Palm Pre/WinPhone 10 better than Android/iOS" side than the one correctly reading trends... (I'm a Perl developer ATM, I clearly don't know a thing about "resume-building")