7 ms·
I'm always reminded of Gary Bernhardt's "the birth and death of javascript" when wasm gets discussed. While it's a bit tongue-in-cheek, I think it really drives
by bocahtie 2y ago
I'm always reminded of Gary Bernhardt's "the birth and death of javascript" when wasm gets discussed. While it's a bit tongue-in-cheek, I think it really drives home that it's really just another layer of abstraction that may or may not be useful for a given problem, and might not be the silver bullet that anyone is looking for. I recon that whether or not wasm will take over everything will mostly be about trade offs between it and the other solutions.
- josh11b 2y agoThat is what I was thinking of too! From 2014: https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript https://www.destroyallsoftware.com/talks/the-birth-and-death....
- tantalor 2y agoYes! I was trying to search for this but I couldn't remember the name.
- afiori 2y agoThis for sure, eg it will never be commonplace to run posgres compiled to wasm. Most instances of "X will eat the world" and "X will be used anywhere" will be false even for very successful technologies