undefined | Better HN

0 pointshmry14d ago0 comments

You're replying to a comment on an article about how WASM does not work fine in the browser

0 comments

The entire article boils down to one specific problem: string marshalling overhead can be optimized to be about 2x faster. Integrating the component model into browsers is overkill for that (and everything else belongs into the toolchains without touching the browser guts).

hmryOP14d ago

> The entire article boils down to one specific problem: string marshalling overhead

No, I don't think so at all. 80% of the article is about other problems (JS bindings are complicated to generate and a leaky abstraction, additional tools beyond the compiler are required, compiler authors don't want to deal with them, they increase the friction for getting started, they're hard to debug, ...)

flohofwoe14d ago

...all those problems should be fixed in the toolchains, not in the browser.

Emscripten exists, DWARF debugging support exists and works (I can step from C/C++ code into JS code and back with the WASM DWARF debugging extension for VSCode), other language ecosystems just need to catch up.

1 more reply

j / k navigate · click thread line to collapse

0 comments

flohofwoe14d ago

hmryOP14d ago

> The entire article boils down to one specific problem: string marshalling overhead

flohofwoe14d ago

...all those problems should be fixed in the toolchains, not in the browser.

1 more reply

j / k navigate · click thread line to collapse