13 ms·
My 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 mu
by jeroenhd 6y ago
My 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.
- tenaciousDaniel 6y agoThat framing makes sense. I've always thought the document model was poorly suited for modern applications. I'm still not sold on canvas itself being the solution - I'd rather open up the underlying accessibility/i18n tech so that developers don't have to reinvent the wheel. But yes, otherwise agree with you.
- vbsteven 6y agoMy ideal solution would be that we can add accessibility apis to canvas. That means we can write GUI toolkits in any language compiling to wasm using canvas apis. Those toolkits gain accessibility support through canvas. edit: some toolkits already have wasm/canvas support (like Flutter and Gtk I think). The missing link is the ability to integrate accessibility.
- domano 6y agoThere are 2 modes you can choose from, one is using html but is less performant.
- 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.