I'll take a bet, use and choose Flutter for a long time.
Anytime that you emulate a platforms UI, if the vendor makes changes, a native widget will take advantage of it a replicated one won’t.
The fact that Google is working on a third operating system (Fuscia) is not exactly a vote of confidence on Google’s ability to focus.
Like I said, you are welcome to distrust Google, but your general assertions are far fetched and stems from Google's product engineering that has to expand and contract its offerings as they are expected to make money unlike its open source projects.
Ever heard of NaCL? Google Chrome Apps? The many abandoned IOT platform (ie Android Things) initiatives? Swift for TensorFlow? App Maker? Fabric? You realize that Google abandoned the original Angular project (AngularJS) and made a completely new incompatible version.
As far as not abandoning “infrastructure projects”, they literally abandoned a physical infrastructure project and left city streets in ruins.
https://arstechnica.com/information-technology/2019/02/googl...
Any of these projects, except angular have the same visibility and impact Flutter has? You're trying very hard to deride Google Infrastructure and its your very generalization that weakens your claims that they should not be trusted. Anyway, I'm done with this thread as far as it goes.
You don't trust them, cool great, but don't make generalizations about what Google is doing because of your distrust.
Angular was “superseded” by a completely incompatible framework causing a major rewrite. Does that bode well for Flutter?
As far as Google not abandoning popular services - remember Google Reader?
Google’s entire promo culture is about engineers and product managers building something new and not maintaining old projects - this is the reason behind 6 messaging apps - three were introduced in one year.
https://www.androidauthority.com/google-messaging-apps-86784...
Not to mention three completely different operating system initiatives - ChromeOS, Android, and Fuscia.
https://bashooka.com/coding/javascript-frameworks-for-cross-...
- via Fable (F# to JS Compiler)
- WebSharper (tightly integrated web frontend and backend)
- Blazor/Bolero Server Side (like phoenix live view)
- Blazor/Bolero WASM
We also start to see Avalonia running on WASM, but I wouldn’t say it’s ready yet.
There are a LOT of friction points that are just really difficult for new devs to work out.
dotnet is really, really good at building scalable, fast, secure web APIs but it is mediocre for building web UIs
This is also reflected in his choice of Xamarin: he "doesn't like" Dart as a language, so he's forced to choose "dotnet MAUI as a platform [which] might not be as mature and capable as Flutter even today". Flutter as well "suffers from many bugs and problems". Is Flutter really that buggy?