6 ms·
That "seamless resize" GIF looks like a joke. I had to reread the paragraph a few times to make sure it doesn't show an earlier stack being now replaced with Fl
by seba_dos1 8y ago
That "seamless resize" GIF looks like a joke. I had to reread the paragraph a few times to make sure it doesn't show an earlier stack being now replaced with Flutter.
- lern_too_spel 8y agoiOS and Android apps didn't support resize until recently. Adding resize support requires additional, though usually small, work (listening to resize events). Presumably, this means that Flutter for Android does this automatically.
- Jare 8y ago> Adding resize support requires additional, though usually small, work Adding good resize support may require a serious rearchitecture of your display engine.
- saagarjha 8y agoiOS does not do live resize, FWIW.
- seba_dos1 8y agoIf resizing is a recent addition there, there's absolutely no excuse for what's seen on this GIF. It literally looks like a "this is why Wayland is better than X11" GIF, showing the X11 way.
- csande17 8y agoYeah, it almost looks okay until you notice the "demo" banner on the top-right sliding in and out of view as the system struggles to update the window layout.
- netdur 8y agoThat means the app is running on VM with debug mode, it is slower than production mode which is native not on VM.
- landr0id 8y agoWhy not run in release mode then to really show capabilities? Poor choice.
- seba_dos1 8y agoSo if hello world is that slow, imagine launching anything non-trivial in debug mode to debug it :P
- CraftThatBlock 8y agoDebug mode has the same performance for 10 lines vs 25k lines, it's really just that it's running in the VM, and has debugging symbol. Performance is almost the same as compiled in my experience, although things like launch and resizing are slower due to how the VM works