38 points ibobev 51 minutes ago 4 comments
sublinear 10 minutes ago | parent
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
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
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