News for hackers. Stuff that matters.
Re:What's new in the .NET 11 runtime by simonask on Wednesday November 11, 2026 @05:06AM (#50451615)
Going to r/csharp over on Reddit is such a weird experience coming from any other background, save perhaps Java. A lot of people just yolo'ing with MockFactoryAbstractFactoryFactory abominations and injecting dependencies into your dependencies so you can inject your dependencies.

A lot of people also seem to have bought into the "Clean Code" dogma popular in the 00s, completely still living in a world where RAM is cheap and JITs are magical.

Add to this the absolutely miserable state of Microsoft's official .NET documentation, and it's a bizarre experience. Everything is "documented" - with things like "Foo(): Constructs a new instance of the Foo class", in case you were wondering what a constructor is...

Context: I'm coming from a background of C++ and Rust. Especially the latter leaves .NET's documentation in the dust, but that doesn't mean the CLR isn't a piece of extremely solid engineering. I'm continually impressed by the .NET JIT and GC, for example, and when you dive into the poorly documented details of the standard library (it's open source these days), you'll see that the quality is very high almost every time.

So yeah, I agree that .NET and C# has everything it needs to be really great in the right hands, but many hands aren't super right.

Re:What's new in the .NET 11 runtime by Squarex on Wednesday November 11, 2026 @06:01AM (#50451977)
Agree, in Java world, most people have migrated from those design patterns, while the dotnet world still seems to be occupied with them.
Re:What's new in the .NET 11 runtime by poloniculmov on Wednesday November 11, 2026 @08:33AM (#50453213)
Is there any book that you'd recommend for modern, sane C# development? I've inherited a .net project and coming from Rails, a lot of things seem plain weird.
Re:What's new in the .NET 11 runtime by simonask on Wednesday November 11, 2026 @08:57AM (#50453494)
I don't know man... Rails seems fairly unhinged to me as well, but it's been a few years since I touched it.

My recommendation is always to understand the technology in depth, then make decisions based on what makes engineering sense. Understand the tools first. For me, that's a hands-on process, but others learn better from books. A lot of programming books seem a bit ideological from a methodological point of view, often written by people who thought they found the magic bullet (see the "Clean Code" fiasco) with perhaps limited time in the trenches.