r/Blazor • u/megadonkeyx • Feb 10 '22 • Gold 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

99% Upvoted

41 comments sorted by

View all comments

3

u/BawdyLotion Feb 11 '22

I’m in the same boat. Blazor is so comfy to work with!

You mentioned using radzen components, while I have a lot of feelings about their ide, I strongly suggest anyone doing rapid development at least test it. It’s suuuuper slick as a way to one click scaffold an existing data set to a working code base. I would argue as soon as you’re past the initial prototype you’ll probably ditch the ide side of things but it just generates a blazor project at its core so all the core functionality is still there to build off of.

Supposedly their 3.0 version will solve basically all the complaints I have with it but given it’s not had much news I won’t hold my breath on that side of it.

1

u/beingmusical Feb 16 '22

I've been using radzen controls for 2 years. They are solid and reliable. The Radzen IDE, s a great pieces of work but once you start tweaking it beyond crud, it can become cumbersome. Had to roll back too may times when changing things produced an error, so I abandoned it and just wrote by hand. It's awesome to spin up a quick nice looking CRUD app with authentication.

1

u/BawdyLotion Feb 16 '22

Completely agree. My approach has been to use it to produce a project boilerplate and then handle any more advanced page logic by hand ditching the ide past that stage.

Still wouldn’t use it in a larger project because the benefits to rapid development would be overlooked by the somewhat unique project structure I’d have to work around down the road but for smaller stuff it’s easy to just pretend the ide doesn’t exist after the scaffolding and start writing your own pages and logic in visual studio