3 ms·

Yes and no, there is a significant bundle size problem with wasm which is hard to fix. I'd rather we just move to native cross platform applications and stop u

Yes and no, there is a significant bundle size problem with wasm which is hard to fix. I'd rather we just move to native cross platform applications and stop using a document browser to build interactive applications. What's more likely is that all of this will probably be eclipsed by LLM and virtual assistants - which could be controlled by native apps with a dynamically generated GUI or voice. I think APIs exposing data and executing functions will fundamentally change what we think the web is.

peutetre 2y ago
> I'd rather we just move to native cross platform applications and stop using a document browser to build interactive applications Here you go. Do both native and wasm: https://avaloniaui.net/ https://avaloniaui.net/ https://platform.uno/ https://platform.uno/ https://flutter.dev/ https://flutter.dev/ Flutter example: https://flutterweb-wasm.web.app/ https://flutterweb-wasm.web.app/
- ec109685 2y ago
  Not that please. The flutter example took 20 seconds to load and the scroll is super choppy. It’s unfortunate there isn’t a more native “app like” UI toolkit. Especially on mobile, web apps generally are bad and a lot of the reason is trying to shoehorn an app experience onto the dom.
  - peutetre 2y ago
    It loads fast for me in Firefox, MS Edge, and Chrome. It's a 2 megabyte transfer and runs quickly. If you're using Safari it's true that Safari's WebAssembly implementation is behind the other browsers. But that's a Safari problem more than a WebAssembly problem.
akira2501 2y ago
> I'd rather we just move to native cross platform applications and stop using a document browser to build interactive applications. Go back to garbage "cross platform" UI toolkits and having to help users manage software dependencies on their machine? No thanks.
wiseowise 2y ago
> I'd rather we just move to native cross platform applications and stop using a document browser to build interactive applications. Cool stuff, let's kill web for good.
kaba0 2y ago
Throwing out the baby with the bath water? There are millions of standardized APIs available in the browser that would be probably impossible to recreate in anything else due to failing consensus.

peutetre 2y ago

> I'd rather we just move to native cross platform applications and stop using a document browser to build interactive applications Here you go. Do both native and wasm: https://avaloniaui.net/ https://avaloniaui.net/ https://platform.uno/ https://platform.uno/ https://flutter.dev/ https://flutter.dev/ Flutter example: https://flutterweb-wasm.web.app/ https://flutterweb-wasm.web.app/

ec109685 2y ago
Not that please. The flutter example took 20 seconds to load and the scroll is super choppy. It’s unfortunate there isn’t a more native “app like” UI toolkit. Especially on mobile, web apps generally are bad and a lot of the reason is trying to shoehorn an app experience onto the dom.
- peutetre 2y ago
  It loads fast for me in Firefox, MS Edge, and Chrome. It's a 2 megabyte transfer and runs quickly. If you're using Safari it's true that Safari's WebAssembly implementation is behind the other browsers. But that's a Safari problem more than a WebAssembly problem.

akira2501 2y ago

> I'd rather we just move to native cross platform applications and stop using a document browser to build interactive applications. Go back to garbage "cross platform" UI toolkits and having to help users manage software dependencies on their machine? No thanks.

wiseowise 2y ago

> I'd rather we just move to native cross platform applications and stop using a document browser to build interactive applications. Cool stuff, let's kill web for good.

kaba0 2y ago

Throwing out the baby with the bath water? There are millions of standardized APIs available in the browser that would be probably impossible to recreate in anything else due to failing consensus.