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 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 think its fine to switch stacks after being in one for two decades. It seems they got into React in a sweet spot where perhaps breaking changes have slowed down...perspective is everything! I bet they would have said something else if they got into React several years ago ;)
6 comments
[ 3.5 ms ] story [ 26.3 ms ] threadAlso 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.