"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.
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.
He ended up on React because it just works and doesn't change all the time. Now both my React and .NET times are some way behind me, but I'd definitely say it's the other way around..
It's changed a LOT over the years though... it's just kind of glossed over at this point... the move to hooks and quasi-functional components was a massive paradigm shift, but most saw it as a raw improvement. I personally think server components are still a bit of a mess and am actively avoiding them for now... they're improving but I think it's a waste of server resources most of the time.
It's a shame that Microsoft sucks at naming projects. ASP.Net is very different in many ways from .Net, of course same runtime infrastructure but the way you do things, the stupid async differences, etc
"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.
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.
I'll save you a few minutes. Guy knew how to build web apps in .NET, had trouble keeping up with the changing ecosystem, switched to React. The end.
He ended up on React because it just works and doesn't change all the time. Now both my React and .NET times are some way behind me, but I'd definitely say it's the other way around..
React has changed far more in far shorter a time than .NET.
It's changed a LOT over the years though... it's just kind of glossed over at this point... the move to hooks and quasi-functional components was a massive paradigm shift, but most saw it as a raw improvement. I personally think server components are still a bit of a mess and am actively avoiding them for now... they're improving but I think it's a waste of server resources most of the time.
Even hooks have changed significantly.
And the React+ ecosystem is in an incredible amount of flux.
And ASP.Net at that..
It's a shame that Microsoft sucks at naming projects. ASP.Net is very different in many ways from .Net, of course same runtime infrastructure but the way you do things, the stupid async differences, etc
thanks