r/Blazor
•
u/megadonkeyx
•
Feb 10 '22
•
1
Two weeks of blazor.. I'm sold
Have been doing development since the 90s and generally have always found the mix of js, html, css and c# to be laborious.
Even react which I find to be the least annoying js framework is painful. Most of the time I would just go back to html, css and jquery to get stuff done quicker.
But blazor, wow, just doing server side blazor for two weeks and I'm making stuff with such little faff. Everything works so painlessly.
Using radzen ui components but not their ide, this is seriously impressive stuff.
Has anyone tested how well server side blazor scales when using azure signalr service? . Now I have used this there's no going back.
119 Upvotes
-2
u/godlikeplayer2 Feb 11 '22
uhm no? it downloads like 1,3mb of javascript for me. Including all that tracking bs and other stuff.
mobile users? hello?
for people who know their js/ts and the established frameworks are most likely still faster. Using blazor for anything outside of throwing a prebuilt component library together is a pain in the ass and requires js skills anyways.
just for the base runtime. Compare that to vue with is like 17kb gzipped. Also, wasm is not as compressible as js and c# doesnt generate the most size efficient wasm binaries.
an example page of blazor wasm downloads like 10+mb https://blazorclientside.computercodeblue.com/
the same page in vue only needs 41kb js https://vue3-realworld-example-app-mutoe.vercel.app/#/
performance is also pretty bad (for now) https://krausest.github.io/js-framework-benchmark/current.html