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.
u/godlikeplayer2 Feb 11 '22 edited Feb 11 '22
first 20, now 5... the fb spa is around an mb of initial downlaod gzipped. The rest are images and other assets that get lazy-loaded.
i guess you have misconfigured something then. 2,6MB is huge for a spa. use compression and a bundler to treeshake and split different views into different chunks and not load everything on the initial page load.
this statement alone shows that you simply don't know what you are doing...
you are funny. Reading your comments I know that you never shipped a frontend to the web.
Accessibility and performance are huge success factors. Amazon found that every 100ms in added page load time cost them 1% in sales.
Also, google takes page load times into account for its ranking as well.
Sure, if you only build some internal apps that just a few people use you don't need to know anything of that, but competing on the web is something entirely different.
again, there isn't 5g everywhere and mobile users a huge part of almost any userbase.