8 ms·
Hmm... on my mid-2014 13" MBP (which is completely fine otherwise) performance is so bad that this doesn't really make me confident that Flutter is "the future"
by flohofwoe 6y ago
Hmm... on my mid-2014 13" MBP (which is completely fine otherwise) performance is so bad that this doesn't really make me confident that Flutter is "the future". Even just dragging windows around stutters (it feels like somewhere between 5 and 10 FPS). Is "native performance" comparable to the web version or dramatically better?
Flutter... stutter... maybe the Flutter team was trying to tell us something all along ;)
- t8y 6y agoI think this is using the HTML renderer. On any other platform it would be using Skia and should be faster. The author could compile the app using Skia on WebGL potentially giving a speed boost.
- jeroenhd 6y agoMy experience with Flutter has been a lot better than what this website demonstrates. I'm not sure how much of the stutter is to be blamed on Flutter and how much is to be blamed on the code architecture of this website. This website is definitely running at 20-30fps max on my phone, whereas 60fps seems perfectly maintainable on my own Flutter experiments with web apps. Having said all that, I'm still miffed about the extreme reliance on Javascript modern web applications have. With the ease of use Flutter promises for making web apps, I can only fear the slow, janky mess that websites will become if the platform ever gets taken up as quick as Flutter seems to hope it will.
- tenaciousDaniel 6y agoThere are at least two projects I know of that are using WASM to implement web applications without JavaScript. Personally I think that’s the future: https://vugu.org https://vugu.org https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor
- dathinab 6y agoThe problem is flutter (web) also doesn't use html/css...
- tenaciousDaniel 6y agoThey re-implement everything in canvas I assume? If so, wow, that’s pretty awful.
- dvdkon 6y agoWhy? At this point, the browser is mostly an app runtime, so I don't think avoiding HTML and CSS is necessarily a bad thing. With some tuning it could even be faster, although I don't think any project has gotten to that point yet.
- tenaciousDaniel 6y agoBecause of the sheer amount of effort that browsers have put into solving all sorts of tricky problems, such as internationalization and accessibility. Once you try to render your own text inputs, you're committing to replicating a mountain of functionality. HTML is deceptively simple.
- vbsteven 6y agoHTML, the dom, css and JS in browsers are far from simple. IMHO we’ve been tacking on more and more “application stuff” on top of a document viewer since the mid 90s. The whole reason React and other virtual dom frameworks exist is to wrangle the original document viewer into an application platform. Yes, after all those years browsers are top notch when it comes to accessibility, but it comes with lots of additional complexity. I am hopeful that with things like WASM and Canvas we are finally starting to move away from this document-based paradigm towards more app-focused paradigms. Although there is still lots of work to be done to make approaches like this work with accessibility tools. Sometimes i think that we are deliberately not adding dom support to wasm in order to not make the same mistakes we did when trying to make html/css/js suitable for apps.
- zenlot 6y agoIs Vugu still developed? Looks like stalled.
- namuol 6y ago> I'm still miffed about the extreme reliance on Javascript modern web applications have. Flutter is written in Dart, which needs to compile to JS or WASM to run on the web, but can compile to native code. I'm guessing the native app is a lot faster.
- fouric 6y ago> This website is definitely running at 20-30fps max on my phone And what specs does your phone have? It doesn't even run on mine - a Moto E6 that is probably representative of the phones used by the average American user, and probably better than the average user globally.
- jeroenhd 6y agoI'm on a Mi 9. It's relatively cheap for the hardware it's got, at the cost of some pretty shitty software I can just deal with. I'm not sure how that compares to the US where there's a 60/40 division in Apple/Android market share, though.
- forgotpwd16 6y ago>Is "native performance" comparable to the web version or dramatically better? Tried their latest ISO[0] on QEMU and... no, it's mostly the same. But based on the release notes VM lag is a known issue. Maybe someone can try it baremetal and tell us how it went. [0]: https://github.com/dahliaOS/releases/releases https://github.com/dahliaOS/releases/releases
- swiley 6y agoIt's probably because they haven't paid attention to software rendering. Many people don't seem to appreciate how well most popular UI toolkits work if your GPU drivers are incomplete or missing. (or if you just don't have hardware that supports modern OpenGL APIs.) This, among other more Googly reasons, is why I'm personally not a flutter fan. It's not like there aren't other decent cross platform UI toolkits anyway.
- nethunters 6y agoOn my mobile dragging windows is smooth. Could be hardware acceleration not being enabled or browser specific.
- 0-_-0 6y agoDo you have HW acceleration enabled in your browser? It makes a huge difference.
- tyingq 6y agoNo stutter on Chrome/Windows on an older Dell Laptop. Maybe it's not doing well with Webkit?
- flohofwoe 6y agoIt's also on Chrome (for Mac), latest Big Sur Beta. Firefox and Safari doesn't work at all (white screen). One reason could be overdraw, the Intel GPUs in older MBPs barely have enough fillrate to render one layer of pixels on a Retina display. E.g. many WebGL demos which render at Retina resolution and either use lots of alpha blending or complex pixel shaders are also stuttering on this setup. Still, an UI framework should never eat away so much performance. Even at full display refresh rate it should only consume a small percentage of available computation power.
- tyingq 6y agoAh, so back to the old "runs best on <browser>" approach :)
- tluyben2 6y agoOn my $200 android phone it is actually rather smooth after the initial download to my browser. Surprisingly so. It performs more fluent than the most apps on my pinephone and so: are there plans to make a native distro? This would make for a nice change as wm.
- Shadonototro 6y agothe problem is not the tech, flutter is perfectly fine it's the developer that uses the tech, or rather misuses the computer you jump to conclusion rather quickly, that's fishy
- dmos62 6y agoI really wish app developers would throttle their prototypes. They tend to run overpowered machines, but then they're oblivious to performance problems their apps have. As a consequence, users have to keep playing catchup with developers' computers. I feel strongly about this. I can't say with a straight face that the growth in apps' resource consumption over the last ten years reflects in improvements in their feature-set. Feels a bit like how gold fish get big if you put them in big aquariums.
- RedShift1 6y agoThis 100x. I've always said, developers should get a Pentium 3 500 MHz and 128 MB of RAM to test their software. And yes I am following my own advise, I use an old Dell with a Core 2 Duo T8100 and 2 GB of RAM to test my software on (oldest I could find at work).
- anthk 6y agoToday I'd choose a Pentium 4/Athlon with SSE2 and 512MB of RAM as the minimum.
- throwaway894345 6y agoI don’t think it’s developers’ devices that are driving the trend as much as economics. Resources get cheaper so people get faster computers and developers can release faster by forgoing optimizations all while delivering the same levels of performance. Of course, this excludes potential customers who can’t afford to update, but those are probably not the folks off of whom app devs are making their money. Of course, this doesn’t legitimize the decision to forego optimizations—I’m only noting that it’s probably not the performance of developer machines in particular.
- dmos62 6y agoI've considered that, but I don't have the impression that app development has gotten faster over the last decade. I bet there's people who can chime in here.
- jchw 6y agoI’m confused. It runs smoothly on my iPhone.
- flohofwoe 6y agoThat's not necessarily surprising, unless your iPhone is also from 2014 ;)
- ilrwbwrkhv 6y agoyes same... lag feels so bad... reminds me of the slack app... at least this one is a whole desktop...
- stephc_int13 6y agoWith the serious slowdown of Moore's law, we should not continue to build apps in such a way that they run like a dog with one leg.