38 points ibobev 51 minutes ago 4 comments

sublinear 10 minutes ago | parent

> On top of all of that, modern browsers also execute WebAssembly, a hardware-independent bytecode format for many other programming languages to target, and which may one day be co-equal to JavaScript on the web.

I skipped around a bit, but when I stumbled onto this opinion I backed out.

This is not the point of wasm at all. Wasm is there as a compatibility layer and for squeezing extra performance out of critical sections of code. The decisions to restrict its API access are very sensible. We can't honestly still be confused about this in 2026.

I excused the python code since a serious browser is not the point, but I'm now suspicious of other intuition-building done throughout the rest of the book.

suriyaG 7 minutes ago | parent

what do you find about this opinion to be a problem?

I've worked with wasm and am fairly familiar with the ecosystem. it sounds like it captures the essence quite well

pavpanchekha 3 minutes ago | parent

Hi, author here! I made a real effort to keep opinions out of the book, and I'm wondering what you feel is opinion above! I don't mean to imply that WebAssembly either will or should be co-equal to JavaScript, just that 1) it's not covered in the book at all, and 2) who knows what the future will contain.

In any case, this line is in the appendix describing what we didn't cover and, per that, we don't say anything else about WebAssembly in the book!

pavpanchekha 6 minutes ago | parent

Hi folks, one of the authors here. Happy to answer questions. Chris and I wrote the book starting in 2019, and the book was largely done in late 2024, with publication in 2025. In case folks are wondering, literally none of it was AI-written, because the AIs didn't exist yet!