Hi HN,
I’m evaluating UI options for a new .NET product and I’m struggling to find balanced, experience-based pros/cons about Blazor (Server / WASM / Hybrid) compared to alternatives (React/Vue/Angular + API, MAUI/WinUI/WPF, etc.).
I’ve seen critical takes like this one: https://alexaka1.dev/blog/blazor-sucks
…but I’d love to hear from people who have actually shipped and maintained Blazor apps.
A few questions I’m trying to answer:
In practice, where does Blazor shine (team composition, product type, deployment model)?
What are the real pain points after 6–18 months (tooling, performance, debugging, interop, upgrades)?
Any “gotchas” that only appear at scale (large component trees, state management, long-lived connections, memory)?
If you had to start a new product today, would you pick Blazor again? If not, what would you choose and why?
Context: this is a long-lived product (multi-year), typical CRUD + some rich interactions, and we care about maintainability and developer velocity.
Thanks for any first-hand advice.
