Earlier quoted context omitted.
Here's some of the explanation about why they chose Dart: > There’s a lot of nice properties of Dart, we talk some about this on our website at our frequently asked questions. One of the nice properties of Dart is that it has a really fast garbage collector, one of the choices that we made in Flutter was to have this reactive style system where it’s very common to allocate thousands of objects in a – if not, tens of…
No one uses Dart. No one is going to switch from React or Vue to Flutter when they can't bring over their TypeScript skills and tooling. It was a stupid, arrogant decision on Google's par, end of story.
Google's cross-platform Flutter UI toolkit goes 1.0
311–320 of 343 posts
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#312Cross-platform frameworks that don’t use native controls have suffered from problems... - They inevitably don’t look or work like native apps in ways both big and small, frustrating and annoying users. (... the spell-checker doesn’t work right or text selection is janky or unavailable where it should be, certain short-cuts work differently or have different gestures or keys, etc.) - they don’t get updates to native c…
Good product is a team effort. The question is: Can you find the right people - not just any people but the right people - to come on-board, use / learn the tools you've chosen, and make magic happen?
Sheer technical prowess of tools and/or people is not enough.
That aside, to your points, there are __always__ tradeoffs. Some more detrimental than others. But again, preserving is a function of team. Someone somewhere is doing what your team is doing, and doing it better. They have the same technologies. So then the question is: why.
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#313Flutter needs to add support for xml styled declarations and Swift
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#314Earlier quoted context omitted.
Two Google teams talking to each other and syncing their agendas and deliveries (or two teams in any big company) is quite a major assumption.
Only one team needs to sync with another in this scenario. It's also assuming that the Flutter team wouldn't consider do that considering they have that kind of information available to them -- it's in their best interest, after all.
I agree with the other commenter -- don’t expect any close cooperation between Flutter and Android because that’s just not how Google (and other huge companies) tends to work.
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#315Earlier quoted context omitted.
Many "native apps" are just "hidden" web apps, users just don't know it.
Such as?
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#316Earlier quoted context omitted.
That's what I thought about Tcl/Tk.
Tcl/Tk is 30 years old. I would be willing to bet my retirement that none of the now-popular presentation technologies will be mainstream 30 years from now. They just don't have that kind of shelf life. If Flutter lasts a decade, it will have lived gloriously. React should be so lucky.
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#317Earlier quoted context omitted.
Most embedded tooling is free nowadays. Free software has eaten the world and will continue to do so. I will use a free UI toolkit when I can. Qt will kill itself with their current pricing model. Automotive is moving towards Android. Qt is not good for medical either because it is not really certifiable.
Actually what I predict is the return to shareware/public domain models, where the free software is only the tip of the iceberg of the stack one actually needs for production code. The trend is already visible with SaaS, Cloud, IoT,... Qt is certainly certified for medical use, https://www.qt.io/qt-in-medical/ . I have hardly seen any big Android Auto adoption. The biggest foe of Qt in Automotive is Web stack.
I have seen two very big Qt projects being cancelled due to Android. Not the Android Auto app but native Android for IVI.
I don't see any indication of your vision for shareware. The trend is towards more and more software being licensed under licenses such as MIT.
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#318Unless they force Flutter upon Android devs, I will let it pass, not eager to learn Dart.
Given the number of times I've seen pjmlp complain about Flutter choosing Dart. I think he/she could have learned the language in less time than writing all of those comments.
"Fool me once, shame on you; fool me twice, shame on me"
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#319Earlier quoted context omitted.
Actually what I predict is the return to shareware/public domain models, where the free software is only the tip of the iceberg of the stack one actually needs for production code. The trend is already visible with SaaS, Cloud, IoT,... Qt is certainly certified for medical use, https://www.qt.io/qt-in-medical/ . I have hardly seen any big Android Auto adoption. The biggest foe of Qt in Automotive is Web stack.
Ok I'll admit I'm not familiar with medical certification. I know that the so called Qt Safe Renderer for ISO26262 compliance is a bit of a joke at least. I have seen two very big Qt projects being cancelled due to Android. Not the Android Auto app but native Android for IVI. I don't see any indication of your vision for shareware. The trend is towards more and more software being licensed under licenses such as MIT.
Which is exactly my point.
Give the tip of the iceberg for free, charge for everything else and give as little back to upstream, if anything.