31–40 of 453 posts
Earlier quoted context omitted.
What’s wrong with using a single canvas? It can be faster. Google Docs and Figma, for example, use canvas rendering
> What’s wrong with using a single canvas You can't even select and copy text. And canvas is inaccessible to screen readers
I was hoping to see better HTML rendering. Using a single canvas to render web apps was my one turn off. Flutter is the right choice for many apps, but not for apps primarily accessed over the Web.
What’s wrong with using a single canvas? It can be faster. Google Docs and Figma, for example, use canvas rendering
did they fix the scrolling on iOS?
did they fix the scrolling on iOS?
> Impeller precompiles a smaller, simpler set of shaders at engine build time so that they won’t compile while an app is running; this has been a major source of jank in Flutter.
Earlier quoted context omitted.
Errr... hang on there. Last I checked Flutter draws their own controls, they're no different than React Native in this context.
React native controls are native to the mobile platform they are running on.
Otherwise, yeah, I think you're right. It's been a bit since I dug around in RN internals.
We have a react native app and sometimes it fails to build. We go to lunch, and come back no code change now it builds. I'm just sick of the NPM/Javascript bullshit. Does Flutter avoid all of these kinds of issues? I'm this close to scrapping the whole thing.
I have an irrational annoyance when projects claim to support "desktop UI" but then only have the most trivial of widgets commonly used in desktop applications. Where is my tree view? Data grid view? Charts? Native file dialog window? From my perspective, while I'm sure Flutter is wonderful, it fits squarely in the "mobile" UI toolkit and "basic" desktop application category.
We have a react native app and sometimes it fails to build. We go to lunch, and come back no code change now it builds. I'm just sick of the NPM/Javascript bullshit. Does Flutter avoid all of these kinds of issues? I'm this close to scrapping the whole thing.
Flutter has its fair share (and to be fair, so do the native toolchains).
I have an irrational annoyance when projects claim to support "desktop UI" but then only have the most trivial of widgets commonly used in desktop applications. Where is my tree view? Data grid view? Charts? Native file dialog window? From my perspective, while I'm sure Flutter is wonderful, it fits squarely in the "mobile" UI toolkit and "basic" desktop application category.
Even Apple's own declarative SwiftUI framework looks like it trails far behind covering rich, comprehensive AppKit apps: https://developer.apple.com/documentation/swiftui/building_a... .