4 ms·
Agree with you on the runtime. Things are better with wasm and wasmgc, but still you can’t use flutter for any website that cares about SEO. However for the “a
by ripped_britches 2y ago
Agree with you on the runtime. Things are better with wasm and wasmgc, but still you can’t use flutter for any website that cares about SEO.
However for the “app” part (after sign in) it’s a one-time download, cached by service worker, only takes a split second.
It would be really nice if flutter could produce a AOT compilation of the “semantic” HTML for the initial page and then hydrate it. Then it’d be pretty similar to waiting for JS bundles for interactivity.
- notpushkin 2y agoMy main gripe is that the DOM backend never took off. The WASM <-> DOM interop is cheaper than ever, especially if you bundle operations so that you don’t need to cross it as often. Still, they decided to implement everything from scratch :-(