One thing I don't like with .NET (at least in C#) is the lack of innovation that we see in other languages such as Java, Go, and Rust. Reading link aggregators to blog posts about C# just gives me the impression that the same ideas and thoughts are repeated over and over.
@patriksvensson I do sometimes wonder how much of this is due to .NET generally being good enough for it's user base. Something something necessity invention. If the platform were worse, or if the user base was different (less Enterprise I guess), maybe the community would innovate more. But it's always been the case the like 90% of .NET developers are "dark matter" and leave it at the office (which isn't necessarily a bad thing, just means less "hobby" work going on).
The weird part is that many teams have abandoned ASP.NET Core UI, and many have adopted JavaScript UIs like React, Angular, or Vue.
Blazor is trying to fix this issue, but in my humble opinion, it’s a little too late.
ASP.NET Core is a glorified JSON generator. That didn’t happen because people “didn’t care”. They cared enough to pick something that worked for them and stopped sitting around waiting.
@khalidabuhakmeh@patriksvensson Totally agree that .NET has lost the front-end, though I'm not convinced it was ever the right fit there (any more than something like C++ would have been a good fit). My thought was more that the majority of .NET users are suitably applying it to problems at their day job and therefore lack incentive to innovate, either feature or time-wise. I.e. the lack of innovation relative to others has as much to do with the makeup of the community as the actual platform.
@daveaglick@patriksvensson Dude… ASP.NET Core’s Razor is sooooooo good. Like so good. I’m seeing what folks are doing with TagHelpers and the loop back to Serverside rendering is a missed opportunity while we were chasing the frontend story. :(
@khalidabuhakmeh@patriksvensson I don't disagree, and rather like Razor over other templating languages (though I still have a soft spot for Liquid). More that the frontend story gradually moved away from monolithic server-side rendering and any non-JS language was going to be a mismatch. Perhaps we're finally starting to unwind that with WASM, but might be too late (or maybe not - but I'm still not convinced Blazor is the answer regardless).
Reading "This week in Rust" inspires me and teaches me new things. Reading similar newsletters about C# just teaches me yet another way to do an EF query, why we shouldn't use the repository pattern, or yet another article about what event sourcing is...
I think the big problem here is that people look at Microsoft and expect them to provide things for them. The .NET community never had a real chance to grow up.
Add comment