I just cannot fathom building on something like Dart with such a tiny market share. The fact that it’s essentially owned by Google (with Flutter being the main reason people, have to, use it) makes it even less attractive. Google only cares about Google so if you step out of line with the “one approved way” you’re going to have a bad time.<p>Google’s commitment, or lack there of, has burned us too many times to give them the benefit of the doubt here. All it takes is someone internally vying for a promotion to come out with “Gart” or “Dutter” with 80% feature parity with Dart/Flutter and billed as “the future”. See: countless examples (Pay/Wallet, 50 chat apps, Health/Fit).<p>I don’t trust Google at all. I won’t build on GCP and I won’t use their languages/frameworks.
What an excellent reasonable article. The fervour around the future of dart and flutter at times seems like people are wishing it abandoned by Google. Certainly dart is pretty much universally disliked on HN for some reason.
This was an interesting read. It seems like the existential fear of Google killing it is currently at a crescendo. Looking around a little I see threads of people talking about those same fears 10 years ago. I wonder what effect that has had on people adopting dart?<p>I really want to love dart, it seems like a great language, but I really dislilke pubspec and its other tooling. Especially the project structure that it forces.<p>I really wish I could use any structure for my project without relative or absolute fs paths, even if it meant it could never be imported by another pubspec project (or import 3rd party deps).