3 ms·
Unlike RN, Flutter is desktop worthy.
by zerr 2y ago
Unlike RN, Flutter is desktop worthy.
- wg0 2y agoHardly. Performance lags. Even after the new rendering engine. Try compiling and then running desk top samples (a mail client, a finance management tool) on macOs and check the amount of jank in animations. Text fields are whole another story. They feel alien in UX on every platform. I can live with that but performance is a deal breaker.
- bschwindHN 2y agoYep, Flutter performance absolutely _sucks_ on older hardware, which they obviously aren't testing on.
- frizlab 2y agoOn newer hardware too.
- bschwindHN 2y agoWell that's a shame, I don't have a new phone at the moment but was assuming it was at least somewhat fast on newer hardware.
- chipweinberger 2y agoWow I have not had that experience on macOS. MacOS support is so good that I've developed a MacOS app just for convenience so I don't need to open the iOS simulator.
- jamil7 2y agoEh, I was recently contracted onto a native macOS team (Swift), the company had an adjacent desktop team who opted to use Flutter, they had a lot of problems and ended up dropping the project. I don't know the details but there was a lot of weird edge cases they ran into on desktop. They had a mobile app partially in Flutter (different team again) which seemed to be OK, however.
- netdur 2y agoThe problem with Flutter is that it's a UI framework that relies on a single main thread. If you put something heavy there, you'll get lag. In contrast, other languages like SwiftUI let you easily spawn threads. Flutter dismisses this as outdated and instead promotes an isolated model with completely separate memory... for reasons.
- jamil7 2y agoOK good to know, yeah, we even have a whole new concurrency model in Swift which makes offloading things a lot safer and easier than it used to be.
- akmarinov 2y agoUnlike Flutter, React is web worthy
- zerr 2y agoReact Native for Web is not quite React.js as I understand.