Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> This is a really cynical take.

I was a Web Forms developers, I've earned at least that. Blazor absolutely does work like Web Forms, in terms of client<->server integration, just because it uses WebAssembly & SignalR instead of JavaScript & Ajax doesn't really change that but rather obfuscates it. Essentially it is just another set of abstractions attempting to paper over a real boundary.

> As in your own quote, Blazor uses SignalR - which uses push-based comms, such as Web Sockets; Web Forms was standard HTTP.

Which makes it even worse, if the client/server boundary wasn't muddied enough with with the unidirectional magic Web Forms used, now we have omnidirectional instead. As if that will make it less complicated and buggy.

Definitely put me in the "nay" category with Blazor. I've danced this exact tango with Microsoft twice before, and their obsession with making browsers desktop-like applications. WebAssembly is cool tech for one day, they're just abusing it for something that is an inherently bad idea.



Uh, have you used SignalR over web sockets? From a performance point of view its going to be much better than Http based polling. Which should make a different when we are talking about updating the UI.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: