That's just like your opinion man ;)

(I'm not a fan of the WASM component model either, but your generalized points are mostly just wrong)

Then give me a counterargument instead of just saying that I'm wrong.

My points are validated by the reality that most of the web is JavaScript, to the point that you'd have a hard time observing degradation of experience if you disabled the wasm engine.

▲

flohofwoe 7 hours ago | parent [-]

I created and maintain a couple of WASM projects and have not experienced the problems you describe:

- https://floooh.github.io/tiny8bit/

- https://floooh.github.io/sokol-webgpu/

- https://floooh.github.io/visualz80remix/

- https://floooh.github.io/doom-sokol/

All those projects also compile into native Windows/Linux/macOS/Android/iOS executables without any code changes, but compiling to WASM and running in web browsers is the most painless way to get this stuff to users.

Dealing with minor differences of web APIs in different browsers is a rare thing and can be dealt with in WASM just the same as in JS: a simple if-else will do the job, no dynamic type system needed (apart from that, WASM doesn't have a "type system" in the first place, just like CPU instruction sets don't have one - unless you count integer and float types as type system"). Alternatively it's trivial to call out into Javascript. In Emscripten you can even mix C/C++ and Javascript in the same source file.

E.g. for me, WASM is already a '1st class citizen of the web' no WASM component model needed.

▲

pizlonator 6 hours ago | parent | next [-]

The fact that you made some webassembly things isn't an answer to the question of why webassembly is not used by the overwhelming majority of websites.

▲

saghm 5 hours ago | parent | next [-]

That's a fairly arbitrary metric. The overwhelming majority of code running outside of the browser on my laptop isn't in Python, but it's hard to argue that's evidence of it being "doomed to being a second-class citizen on my desktop indefinitely".

▲

flohofwoe 6 hours ago | parent | prev [-]

> why webassembly is not used by the overwhelming majority of websites

This is such a bizarre take that I don't know whether it's just a trolling attempt or serious...

Why should web-devs switch to WASM unless they have a specific problem to solve where WASM is the better alternative to JS? The two technologies live side by side, each with specific advantages and disadvantages, they are not competing with each other.

	▲	pizlonator 6 hours ago \| parent [-]
		> This is such a bizarre take that I don't know whether it's just a trolling attempt or serious... I'm being serious. > Why should web-devs switch to WASM unless they have a specific problem to solve where WASM is the better alternative to JS? They mostly shouldn't. There are very few problems where wasm is better. If you want to understand why wasm is not better, see my other posts in this thread.

▲

skybrian 6 hours ago | parent | prev [-]

What toolchain do you use to build your apps?

	▲	flohofwoe 6 hours ago \| parent [-]
		Vanilla Emscripten. Most of the higher level platform abstraction (e.g. window system glue, 3D APIs or audio APIs) happens via the sokol headers though: https://github.com/floooh/sokol