2/11/2026 at 5:23:26 AM
"React as the stack"? If you're talking about the very top of the stack, sure. Not sure how React replaces .NET otherwise to be honest. Saying that the React (I assume Node on the backend) and overall JS ecosystem is stable compared to modern .NET is an interesting take to be sure :)Also I feel that the author might have given up on .NET just at it became really good. It's been very consistent for many many years now. The last few years major upgrades (from .NET 5 I feel) have been very simple. I also had an adjustment period from older WF / EF / MVC etc somewehere around when .NET Core 3 hit, but I feel that the fundamental patterns have carried over well.
Big disclaimer: I don't use .NET on the frontend. Blazor is interesting but would probably not consider it for anything more than simple internal tools.
by tehsuk
2/11/2026 at 5:50:04 PM
I'm largely of the same mindset... I find the current .Net tooling for the backend to be pretty great. C#, Dapper and FastEndpoints FTW. I still really like JS/TS tooling with Hono and Rust with Axum though... but C# today is pretty great for backend work.I'm also not a fan of Blazor... it's bloated and heavy in client usage, and server mode has all the down sides classic Web Forms did. Not a fan at all.
I tend to still like React with Redux+thunks and MUI or Mantine for the components. Very little comes close to it.
by tracker1