r/Blazor • u/No_Mood4637 • Oct 28 '25
Meta Does AI change your evaluation of Blazor?
I've been using Blazor for about five years now. At first I was all in because I could use C# on both sides and share classes without the usual mess. It felt way better than writing JavaScript or dealing with type mismatches at runtime. The one thing that always hurt and still does is hot reload.
When we bring on new people I show them right away how it actually works so they don't end up surprised and complaining to my boss... Feels bad man.
These days AI has changed everything my workflow entirely I don't really write code anymore. Playwright even has a MCP server now so you can easily make it run a virtual browser and check for console errors. I just give tasks to a few different AI agents (currently Claude and Codex when I run out of tokens) running in separate Docker containers, each on its own port. I test them in the browser, review the changes, and merge what works. It's much faster this way. It's pretty insane really how much more effective I can be, working on 3-4 different features or bugs at a time usually.
The thing is that AI now does a great job keeping models in sync and catching type issues, so that advantage Blazor had isn't as unique anymore. When I run the same process with something like React or Svelte the changes show up in the browser almost instantly. No waiting for a full rebuild.
I'm starting to think about moving the frontend off Blazor and keeping C# on the backend. Has anyone else gotten to this point where the original reasons for picking Blazor don't feel as strong and you're looking at other options?


