It would also enable combining different languages with high-level interfaces rather than having to drop down to c-style interfaces for everything.

The c-style interface of wasm is pretty limiting when designing higher level interfaces, which is why wasn-bindgen is required in the first place.

Luckily, Firefox is pushing an early proposal to expose all the web apis directly to wasm through a higher level interface based on the wasm component-model proposal.

See https://hacks.mozilla.org/2026/02/making-webassembly-a-first...

I think you're missing the point they're trying to make. It's not that the problem isn't real, it's that the solution won't work. Kids will find a way around. They have a lot more free time than us.

I've actually tried to do that the past and got pretty far. https://github.com/wasi-gfx/webidl2wit

And here's the generated wit https://github.com/mendyberger/brow

Modern languages come with lots of interesting features like better dev ex, null safety, etc. Js is a fine language, but there are other languages that bring unique advantages, the web shouldn't block developers from using better tools. The web is best off when developers have freedom.

> it doesn't seem like this should be possible on a Linux server

Some real misconceptions here

> at the time just about everyone believed that hacking the system was impossible.

Bit of a nitpick, but I don't think saying things like this to normies is a good idea. Every system is hackable.

For me, having wgpu's rust native api feels so much nicer than having to deal with the unergenomic web_sys api. Tradeoffs.

Comments URL: https://news.ycombinator.com/item?id=46201463

Points: 7

# Comments: 2