Michael Shpilt, a .NET developer, writes about C# performance, memory leaks, caching, and choosing a .NET web tech stack.
HN commenters cite it for its JSON serializer benchmarks and ORM performance comparisons, using it as a reference when discussing .NET Core library speed.
I Googled “.NET assembly loading”. The second hit is “Understanding How Assemblies Load in C# .NET”, [0], from July 2020, 4 months before the RTM release of the unified .NET 5. While this post mentions .NET Core by name once, this post is completely irrelevant to .NET Core/5+ (which threw out the Global Assembly Cache, assembly redirections, and generally simplified everything). How do you find articles that are actually relevant to the modern .NET and not the Framework?
The Java stuff is easy. From the perspective of a Java developer, most of the things you listed (except for ME, EE and JavaBeans) are just “Java”. And they always have been.
[0] https://michaelscodingspot.com/assemblies-load-in-dotnet/
I would love to here some MSFT people who work on the Net Core teams thoughts about these libraries, because it seems the community has really amazing things to contribute, such as this string builder library.
Net Core has seen amazing improvements compared to Framework, yet often still falls behind existing community offerings.
e.g. UTF8JSon library: https://michaelscodingspot.com/the-battle-of-c-to-json-serializers-in-net-core-3/
Outperforms the new Net Core json library.
HyperLinq:
https://medium.com/@antao.almada/netfabric-hyperlinq-zero-allocation-fe5d0dd6b1a6
Is basically Linq with 0 allocations.
What is blocking MS from integrating these approaches into Net Core?
Decoding JSON is surprisingly intensive. Check out this to see what's going on with it in Dotnet: https://michaelscodingspot.com/the-battle-of-c-to-json-serializers-in-net-core-3/ .
Node.js will have that issue and in fact the stdlib JSON encoding/decoding can't even be paused so once you start a processing something you're stuck until it's done. You could, however, write an incremental serializer/deserializer that could spread processing out across many event loop cycles to mitigate.
Go, ASP.NET, and others not so much, depending, because the schedulers can pause and resume the tasks(on top of being threaded).
Modern ORMs are pretty efficient [1]. Some developers use the ORM for the "write model" and native SQL for reads/reports, if you are read-heavy.
[1] https://michaelscodingspot.com/npgsql-dapper-efcore-performance/