I previously wrote about the excitement around WebAssembly and, having seen many technologies like this come and go in the past, my analysis of why WebAssembly might be a bad idea. In summary, it’s not that it is technologically bad – it’s simply that I don’t see a space for it in a world where computing power has been becoming thinner on the client-side for years and microprocessor prices are skyrocketing.
(And yes, I know that WebAssembly can also run on the edge of the server-side. So can a lot of things, so whilst it’s interesting I don’t see much of a point of it there either except where performance is paramount and computational cost is high).
The new Web Assembly 2.0 specification can be found here:
- WebAssembly Core Specification Version 2.0, describing the next version of the core standard.
- WebAssembly Web API Verson 2.0, describing the integration of WebAssembly with the broader web platform.
WebAssembly remains a technology to watch, but I suspect mainstream adoption and market penetration will be difficult for it to achieve against stalwart web development platforms PHP and nodeJS.