News for hackers. Stuff that matters.

A comment on Rendering Blazor components to a string: Exploring the .NET 8 preview – Part 9. Parent comment

Re:Rendering Blazor components to a string: Exploring the .N... by bradleyishungry on Thursday October 12, 2023 @10:10AM (#37857403)
I've used blazor on a couple larger projects, mostly wasm blazor, and have used components in hacky ways on occasion (reflection, interpolation, etc). Some of these components are pretty large and I have never once had a crash from those projects in any IDE, be it VS2022, Rider, or the trash that is VS for Mac. Not downplaying your experience, just saying blazor projects have been very solid to work with on my end.
[ Parent | on HN ]
Re:Rendering Blazor components to a string: Exploring the .N... by pathartl on Thursday October 12, 2023 @03:34PM (#37862018)
Throwing my hat in saying I agree with you. There are certainly aspects of Blazor that need to be improved, though. Sometimes Intellisense has an aneurism and syntax highlighting completely breaks. Debugging needs some TLC in instances where exceptions are thrown in the JS console instead of being caught by the VS debugger.

I have experienced _some_ performance problems, but only when I don't have enough resources for VS to gobble up. Should it be lighter? Absolutely. It's not like I can't get work done though.

[ Parent | on HN ]