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/propostor Feb 11 '22 edited Feb 12 '22
We aren't all trying to rewrite Amazon
Amazon looks like it was written in 1998 and never updated and is slow as fuck so I don't know why you use that as an example.
The only place I see people talk about download size of SPAs is in boring dick-swinging matches on the internet where they try to look like they're a web development ace because "this framework is smaller than that framework". Seriously no one cares, I already told you development time is more important than a few kilobytes difference in initial download. Server latency is usually a bigger factor than how many kB your website is.
5G, 4G, H+, 3G, whatever. Again, no professional developer halts production and goes into emergency mode because their users in the mountains with poor signal might have trouble connecting. WTF point are you trying to make regarding mobile phones, I don't get it.
If you're going to accuse me of never releasing any website then I'll just do the same and accuse you of only releasing toy projects that nobody is ever going to use, because if your main result is the proud ability to look in the mirror and say to yourself, "Yeah, that website was SMALL", you really aren't developing anything of value. In all my years nobody anywhere at any level has ever made framework size the defining issue. Conversely, we're now writing a Blazor project at work and everyone is amazed at how fast development is. And so I go back to my original point - development time is important. The only area of optimisation I've ever seen focused on is server speed and database query efficiency, because that can get ugly pretty fast if you don't know what you're doing (unless you're only writing a toy website where the only thing worth caring about is how many kB it is on the client side).