I'm no Google apologist, but Flutter really does seem to be something special.
I've worked with a few other "write once, run anywhere" frameworks before, and Flutter is by far better. Dart is C# with the flexibility of JavaScript, Flutter's package management is like NPM but good, ant hot reloading saves a ton of time (when it works, at least).
I wasn't sold on view-as-code at first, but it does start to make sense after you use it for a bit, and the type protection you get is a bonus.
So yeah, I wouldn't discount Carmine's opinion right away. The hype is somewhat valid, IMO.
I might be getting over excited and Google doesn't have the greatest track record, BUT:
Flutter is open-source;
Flutter is an integral part of Google's strategy regarding mobile and desktop platforms, together with the Fuchsia OS.
Regarding React Native I can say two things:
it is simply a big and heavy abstraction layer over the Android and iOS SDK, unlile Flutter which renders its own widgets;
learning Dart doesn't take almost any effort at all if you know JavaScript and have ever used any other moden language in your life;
I would much rather define UI in Dart in a simple and coherent syntax rather than using XML/HTML-like syntax in the middle of my code to define UI.
Flutter’s desktop, Web and embedded devices support is the most revolutionary part about it, and it actually already works, even though it isn't very stable and mature yet.
The conclusion is, as many Italians would say, "Ai posteri l'ardua sentenza": only after everything has unfolded will we know who was right on this.
Anyway, thanks for the comment, I always appreciate hearing opinions on my posts and on Flutter, even when they're negative, and my attempts to refute your analysis aren't supposed to be taken as a dismissal of your opinion, but rather as a way to mutually reach a deeper understanding of the matter.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Crikey, somebody's getting a bit overly excited.
I think I'll stick with react native for now and wait for this along with 50 other Google new emerging systems to go into the archive.
And please, bindings or not, we don't need another language to learn.
I'm no Google apologist, but Flutter really does seem to be something special.
I've worked with a few other "write once, run anywhere" frameworks before, and Flutter is by far better. Dart is C# with the flexibility of JavaScript, Flutter's package management is like NPM but good, ant hot reloading saves a ton of time (when it works, at least).
I wasn't sold on view-as-code at first, but it does start to make sense after you use it for a bit, and the type protection you get is a bonus.
So yeah, I wouldn't discount Carmine's opinion right away. The hype is somewhat valid, IMO.
I might be getting over excited and Google doesn't have the greatest track record, BUT:
Regarding React Native I can say two things:
Flutter’s desktop, Web and embedded devices support is the most revolutionary part about it, and it actually already works, even though it isn't very stable and mature yet.
The conclusion is, as many Italians would say, "Ai posteri l'ardua sentenza": only after everything has unfolded will we know who was right on this.
Anyway, thanks for the comment, I always appreciate hearing opinions on my posts and on Flutter, even when they're negative, and my attempts to refute your analysis aren't supposed to be taken as a dismissal of your opinion, but rather as a way to mutually reach a deeper understanding of the matter.