Earlier quoted context omitted.
Which is irrelevant to my point, which is that it's also used where it's not native.
So Cocoa is missing from your list given iTunes on PC.
[deleted]
Google's cross-platform Flutter UI toolkit goes 1.0
131–140 of 343 posts
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#132Like I said yesterday "The road block for adoption will be Dart. Why they didn't just choose Typescript or go with native javascript is beyond me. No one uses Dart. It was probably the poorest design decision they could make."
The comment from pzo points out an even worst of an adoption showstopper.
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#133Earlier quoted context omitted.
For bonus points you've probably broken accessibility on many platforms as the way that a11y works is intrinsic to the native widgets used by a platform.
I wouldn't assume that. It's literally the number one thing people bring up with custom UI components, I'd be very surprised if Flutter ignored the issue.
Oh I'm sure they didn't ignore is, just that you're constrained to platforms that allow a side-channel mechanism to expose a11y and handle focus+navigation.
I haven't looked deeply at the HTML5 APIs but if you wanted to say port Flutter to HTML5 Canvas you may run into problems where you can't expose rich enough a11y primitives on something that was just meant to be a bitmap.
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#134Cross-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…
> - They inevitably don’t look or work like native apps in ways both big and small, frustrating and annoying users. We're way past that in the mobile world, where both Google, Facebook, and other top dogs use non-native cross platform frameworks and looks (e.g. Material UI).
Same in the desktop world - Qt emulates the widgets, but can theme them, then QML is another story. Also WPF (from what I've heard) uses (skia?) to paint own widgets. IMGUI is another example.
Then using the native wrappers, like wxWidgets is often cumbersome to create customized control, and if you do you end up with some platform specific version (not end of the world, but pretty much why not use the OS toolkit directly). Also any wrapper soon or later suffers from "leaky abstraction" - where you hide things behind interfaces, but can't hide different performance characteristics, and getting the current line in a log dialog might just kill you, because underneath it might be scanning all '\n', '\r' until your cursor position.
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#135Earlier quoted context omitted.
Then why bother to post to complain? Is it necessary to also post in React Native threads about how that framework does not fit your needs?
Because Flutter would be a nice framework to use if they hadn't decide to bet on a language struggling for survival outside Googleplex. React Native uses a programming language widely accepted, no need for complains.
You said you can't be bothered to learn dart because you want to build your skills in c# etc. As a result the only criticisms you can make are devoid of content: It's not a proper, modern language (what?). It's struggling for survival...
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#136Google is spending so much money on Flutter , it’s insulting. Honestly, the entire industry is shifting towards JavaScript/Typescript and the only language that they could think of for Flutter is Dart ? This is even more Hypocrite knowing that Flutter doesn’t actually run the Dart VM, it uses AOT and compile to native code. Meaning we could use literally any ECMAScript language to run with Flutter instead of Dart. Th…
Dart was designed by one of the guys who created the V8 JS engine.
I'm pretty sure if anyone was justified to create a new language here it would be those guys.
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#137I have made an (unofficial/private clone of) Azul boardgame in Flutter (intended as a christmas present to my wife).
Whithout having any Dart or frontend or UI experience (I have always progammed backend and CLI apps), I could make a simple working game in maybe 10 hours - and it is mainly due to the instant feedback cycle.
The whole thing is less than 600 lines of Dart code. (and about 100 lines is to deep copy game state objects (for the undo functionality) as Dart can't do that automatically.
The design is simple, just circles, shadows and small animations (the player in turn gets magnified)[1], but with zero experience in the UI domain I actually barely beleive that I have made it ;)
Of course games are absolutely not affected by the native or not native widget issues, and also I did not use any advanced services from the platform, so can't say much about those weaknesses.
I was really happy with it, I would definitely recommend it to similar hobby/beginner projects.
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#138Like I said yesterday "The road block for adoption will be Dart. Why they didn't just choose Typescript or go with native javascript is beyond me. No one uses Dart. It was probably the poorest design decision they could make." The comment from pzo points out an even worst of an adoption showstopper.
They won't stop pushing Dart, thanks to success of Go, yet another 'good enough for the job' mediocre (at best) language.
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#139Earlier quoted context omitted.
You mean the OS that is developed independently from Android with completely separate teams and that nobody knows where it will be in 2 years ? Since this is Google we are talking about, no warranty that this will ever go on one of their flagship phones.
That's just a senior dev retention project.
Or maybe not, and that's Android vNext.
Re: Google's cross-platform Flutter UI toolkit goes 1.0
#140Google has a history of introducing products and then killing them. For developing mobile apps they currently support "vendor native" via Android Studio using Java or Kotlin, Progressive Web Apps, and now Flutter. Will Google really support all three over the long term?
From my point of view it looks a big internal politics war. Whoever wins, we loose.
What we loose if Android side wins?