Too bad Android diverged too far from the rest of the Linux world and isn't using Wayland.
For Flutter it doesn't really matter because all it needs is a canvas to paint on.
Graphical User Interface Using Flutter in Embedded Systems [pdf]
41–50 of 202 posts
Re: Graphical User Interface Using Flutter in Embedded Systems [pdf]
#42Dart is easily my favorite programing language. It's the best parts of C# plus real dynamics. The Flutter ecosystem is already above and ahead of React Native , a big part of it is it doesn't have the baggage of npm, Babel and JavaScript. For a friend's side project I've been using Flutter Web and I couldn't be happier with it
It's unfortunate that the web mode uses a canvas and won't work with native browser accessibility stuff. That was the show stopper for me last time I've tried it.
(disclaimer: I work on Flutter Web)
We actually use plain standard HTML and ARIA attributes for accessibility. If you don't see them, try enabling a screen reader (e.g. TalkBack on Android, VoiceOver on iOS/macOS), then you'll be able to enable accessibility in the app. If you are having problems with a11y, please file a github issue. A11y is very important to us.
Re: Graphical User Interface Using Flutter in Embedded Systems [pdf]
#43Somewhat of an aside, since this article is about Flutter on embedded systems where React Native isn't even a consideration but... I've used both Flutter and React Native. Hands down, Flutter is the more enjoyable experience. Everything from the language, to the toolkit, to the IDE, to the final product, is just BETTER. React Native is a bloated, hacky, slow, garbage pile by comparison.
I can't figure out flutter. I see so many rave reviews. But I personally tried it and strongly disliked it. The toolkit and Android Studio run horribly slow - like really slow. And the output is basically this generation's flash. Some of the samples I tried on their gallery are mediocre. Very slight, but noticeable sluggishness. Some are just terrible; the 2d transformations moves at like 7fps. Plus there are so many…
I've been following Dart since it's first release in 2012. I was able to be productive with right away back then. The JavaScript community freaked out because some Google exec in an email said Dart was a JavaScript killer. That did a lot of damage to it's acceptance. Dart was written with 2 things in mind afaik: 1) Replace Java based Google Web Kit used to write JavaScript (GMail circa mid 2000's) and 2) to serve as a backup language in Google lost the Java lawsuit with Oracle. Dart wasn't designed to be a shiny new thing like Swift, Rust or Kotlin, but more of a working language for day to day needs at Google. By those measures, Dart has succeeded admirably with Flutter taking off in popularity. Dart drew a lot of inspiration from C#, so I don't understand that complaint. C#, TypeScript and Dart are similar languages. Finally, Flutter/Dart should be compared to Blazor/C# and I think by that comparison, Flutter wins hands down.
Re: Graphical User Interface Using Flutter in Embedded Systems [pdf]
#44Honestly I don't get the appeal of Dart/Flutter for this use case for two major reasons: 1. Dart is garbage-collected; and 2. Dart has optional typing, which is to say it supports type hints but is essentially dynamically rather than statically typed. This presentation claims low overhead so I'm open to be proven wrong here. I wonder how much of that (if true) is Flutter and how much is Wayland (over X). I'd really l…
> 2. Dart has optional typing, which is to say it supports type hints but is essentially dynamically rather than statically typed.
Dart has not been optionally typed since Dart 2 (released in 2018).
Re: Graphical User Interface Using Flutter in Embedded Systems [pdf]
#45I always like the notion of "it's lighter weight and has fewer dependencies... but it doesn't work right". ;-) It'll be interesting to see how much Wayland can remain lighter weight once it has accounted for all the "not working right" cases.
[deleted]
Re: Graphical User Interface Using Flutter in Embedded Systems [pdf]
#46Flutter looks great, and I seriously considered it for my next project. In the end I decided the possibility of Google getting bored and ending support was enough to tip me to using Qt Quick instead - even though I kinda dislike Qt and js, and will have to pay for it.
Well, Flutter is open source, so even if Google dropped support (extremely unlikely), it will likely continue on.
Re: Graphical User Interface Using Flutter in Embedded Systems [pdf]
#47Earlier quoted context omitted.
Interestingly, Wayland is used to some extent in Chrome OS, including for bringing Android apps into the windowing system. See e.g. https://qiangbo-workspace.oss-cn-shanghai.aliyuncs.com/2019-... The implementation includes some interesting projects like Sommelier, a Wayland protocol proxy used as part of a setup to virtualize host resources safely: https://chromium.googlesource.com/chromiumos/platform2/+/HEA...
Yeah, I've seen that. I wish Android would close that gap and switch to standard Linux stack.
There's a reason it doesn't use the standard Linux stack: the standard Linux stack is a garbage fire. Throwing away the userspace of Linux Desktop and replacing it is what allowed Android to thrive.
Re: Graphical User Interface Using Flutter in Embedded Systems [pdf]
#48I'll be the contrarian: Is this a good business decision? Sony has recently stated that it wants to enter the automotive industry but Google is a direct competitor with Waymo and their Nest product has a pretty firm standing in the smart home appliance environment. Is it wise to basically become dependent on a large competitor for such an integral component of your next generation products? What if Google decides to…
I think it's a side-effect of wider adoption. NPM/Node suffers the most from this. I would also argue that Rust is experiencing a little of this.
Re: Graphical User Interface Using Flutter in Embedded Systems [pdf]
#49Somewhat of an aside, since this article is about Flutter on embedded systems where React Native isn't even a consideration but... I've used both Flutter and React Native. Hands down, Flutter is the more enjoyable experience. Everything from the language, to the toolkit, to the IDE, to the final product, is just BETTER. React Native is a bloated, hacky, slow, garbage pile by comparison.
I can't figure out flutter. I see so many rave reviews. But I personally tried it and strongly disliked it. The toolkit and Android Studio run horribly slow - like really slow. And the output is basically this generation's flash. Some of the samples I tried on their gallery are mediocre. Very slight, but noticeable sluggishness. Some are just terrible; the 2d transformations moves at like 7fps. Plus there are so many…
Were you running debug or release builds? Your experience with sluggishness is very atypical.
Re: Graphical User Interface Using Flutter in Embedded Systems [pdf]
#50Earlier quoted context omitted.
I can't figure out flutter. I see so many rave reviews. But I personally tried it and strongly disliked it. The toolkit and Android Studio run horribly slow - like really slow. And the output is basically this generation's flash. Some of the samples I tried on their gallery are mediocre. Very slight, but noticeable sluggishness. Some are just terrible; the 2d transformations moves at like 7fps. Plus there are so many…
I've been following Dart since it's first release in 2012. I was able to be productive with right away back then. The JavaScript community freaked out because some Google exec in an email said Dart was a JavaScript killer. That did a lot of damage to it's acceptance. Dart was written with 2 things in mind afaik: 1) Replace Java based Google Web Kit used to write JavaScript (GMail circa mid 2000's) and 2) to serve as…
If Flutter had a Bolero/F# analogue, that would be a very quick adoption reason for me