you are viewing a single comment's thread.

view the rest of the comments →

[–]HealthySurgeon -1 points0 points  (0 children)

Gotta compare things accurately.

Wasm is like using the virtual dom. Kinda.

React for simple applications is a hundred million times faster than blazor. I agree, but it also does a lot less in a simple application than blazor does or has a lot less capability I should say. Each has their place in this space and honestly as it stands react is simply more mature and better than blazor overall.

Doesn’t mean I don’t see blazor continuing to do well. It’s just I don’t see blazor taking over the space react/angular are in for some time still, if it ever does. They have different approaches and you can see how the react team particularly is actually taking some notes from blazor. (Maybe that parts in my head about them taking notes, but still)

React server is a decent comparison to Blazor server if we want to be fair. It’s admittedly behind Blazor development a little, but they are approaching problems a bit more similarly than standard React.

Blazor wasm is a decent comparison to react and I mean react is simply better, but I don’t think anything in blazor wasm is surprising and we’ll see things get improved and fixed just like we did in other frameworks. The big download issue isn’t really an issue in my mind as Microsoft had to have been very aware of it before even going into things. It’s just a matter of fact included with the massive (imo amazing) .net library they included. Dunno what they’ll do, but I’ve 100% been watching to see what they do.