The idea isnt new though, GWT has been around since 2006 (the ancient Java version of writing the frontend code in Java, which is then served as JS to the client)
I dont think we're going to go back to that anytime soon, the performance hit is just too big compared to a well written js implementation.
To be fair, Blazor uses wasm, which is significantly better then the cross-compilation of GWT back then. nonetheless, the performance (esp. time to first render) is just not good enough for a lot of consumer facing apps
It definitely has its niche though.
Especially if you're able to cache the .net runtime that gets executed through wasm locally (PWA style)
I dont think we're going to go back to that anytime soon, the performance hit is just too big compared to a well written js implementation.
To be fair, Blazor uses wasm, which is significantly better then the cross-compilation of GWT back then. nonetheless, the performance (esp. time to first render) is just not good enough for a lot of consumer facing apps
It definitely has its niche though. Especially if you're able to cache the .net runtime that gets executed through wasm locally (PWA style)