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
gregopet|19 days ago
tracker1|19 days ago
lenkite|18 days ago
LarsKrimi|19 days ago
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
Lapsa|19 days ago