3 ms·
> That's not easy and I suspect it's not solvable by technical means solely. So it's hard. And it's easier to just write blog posts that complain again and agai
by giancarlostoro 7y ago
> That's not easy and I suspect it's not solvable by technical means solely. So it's hard. And it's easier to just write blog posts that complain again and again.
That would be WebAssembly and its true since it is progressing a bit slowly but thats a good thing. If they get it right you can write JS to WebAssembly thats modern and backwards compatibility wont matter or write Python to WASM, or Rust, Go, C#.... And so on.
Someone mentioned here on HN ages back that WASM will probably be the next stage after SPA frameworks. I think C#'s Blazor project is a strong indicator that what is to come will be pretty damn good and pretty damn powerful.
Granted it will take a while as WASM matures and we make sure to push users towards modern browsers. I think tech like Blazor will even see old tech like ActiveX or Java Applets find their replacements in WASM. Heck we saw the other day a full blown Flash Player Emulator in Rust for WebAssembly. That was quite well done!
The future is in WASM and it will take a bit to get it just right but at least we can work on making sure it is designed properly. Do what Microsoft did: they learned from Javas mistakes and C# became a really good language. Lambdas in Java took forever to be added.