3 ms·
Well - the problem is... the "in theory" means that nobody will bet on WASM if it is not really going to be useful. People use HTML, CSS, JavaScript - that has
by shevy-java 9mo ago
Well - the problem is... the "in theory" means that nobody will bet on WASM if it is not really going to be useful. People use HTML, CSS, JavaScript - that has been shown to be very useful. WASM is not useless but how can people relate to it? It is like an alien stack for most people.
- frez1 9mo agoThe way things usually gain traction is when a big tech company has success experimenting with it. it happened with node way back and happening with rust now. the fact we haven't heard much about was use is probably because it isnt as valuable as we think, or no one has played around with it yet to find out
- matt_kantor 9mo ago> when a big tech company has success experimenting with it TFA has many examples of big tech companies using Wasm in production. It's not exhaustive either, e.g. the article doesn't mention: - Google using it as a backend for Flutter and to implement parts of Google Maps, Earth, Meet, Sheets, Keep, YouTube, etc - Microsoft using it in Copilot Studio - eBay using it in their mobile app - MongoDB using it for Compass - Amazon supporting it in EKS - 1Password using it in their browser extension - Unity having it as a build target (And this was just what I found with some quick web searches; I'm sure there are many other examples.) --- > the fact we haven't heard much about was use is probably because it isnt as valuable as we think One of the conclusions of the article is that it's mostly used in ways that aren't very visible.
- azakai 9mo agoIt is totally fine if most people don't relate to wasm - it's good for some things, but not most things. As another example, most web devs don't use the video or audio tag, I'd bet, and that's fine too. Media, and wasm, are really important when you need them, but usually you don't.