Hacker News Reader

Comment by tdrdt | Hacker News Reader

I write a lot of apps in Blazor. And I also think this is where we are heading. Just write code in C# and it works. Unfortunately Blazor feels a step back compared to something like VueJs but I really like that I don't have to write JavaScript anymore.

View on HN

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 really like the Blazor tech, but with all the activity around Blazor WASM I'm not sure this is really where things are heading. It's neat that both options work with the same underlying tech(even if converting an app between the two wouldn't be so simple).

I've built frontends in React and feel I have a fairly high level of expertise in VueJS; I actually got the sense that Blazor borrows quite a few ideas from VueJS. A major missing component IMHO is a good reactive state store like MobX..

Reply on news.ycombinator.com