News for hackers. Stuff that matters.
Re:Improving C# Memory Safety by Quothling on Saturday May 23, 2026 @11:18AM (#48248421)
Around here C# is only really used at stagnant middle sized companies with horrible code bases. The sort where the company follow Uncle Bob religiously, while completely misunderstanding everything Uncle Bob ever said. Doesn't mean the language (and it's runtime) can't be good.
Re:Improving C# Memory Safety by caspper69 on Saturday May 23, 2026 @12:20PM (#48248927)
Yes, many people instinctively stay away from anything microsoft (except github, typescript and npm). But the stack is solid. I’m always reminded of Stack Overflow and how they built on asp.net and like 7 servers and it scaled very well for years.

Everyone has what they like and what they’re familiar with, and for better or worse, especially for startups it’s rarely .net. But I couldn’t imagine e.g. using js instead on the back end, but that’s just me.

Re:Improving C# Memory Safety by Weebs on Saturday May 23, 2026 @12:56PM (#48249203)
A VM with good FFI and structs is pretty unique and all of the tooling around .NET is excellent

F# is a sleeping giant of capability in the FP/ML space, being able to use a lot of the existing tooling

People rightfully point out how it's sort of second class in comparison to C# at times, but its still A tier tooling that few languages have

Re:Improving C# Memory Safety by legulere on Saturday May 23, 2026 @03:53PM (#48250833)
The examples in Clean Code show that Uncle Bob himself misunderstood heuristics as strict rules that are to be taken to the extreme. There's nothing to not misunderstand.