Hacker News Reader

Comment by dvxvd | Hacker News Reader

So.. since 2018.. it was 2.5 years ago.. and nothing changed? Obviously, who cares about ex-customers.. fresh one are generating bigger bonuses...

View on HN

It was fixed.

https://github.com/dotnet/runtime/issues/8744

Not completely. I've seen hard deadlocks on ReaderWriterLockSlim on high thread counts on 8+ core nodes on .Net core (2.1). Literally all threads in a process jammed on spin waits. This is especially frustrating as the concurrent collections sit on top of that steaming pile of crap.

I've learned to walk in the opposite direction of .Net now.

Replying to self as I can't edit this now. Whenever I am critical of the .Net framework or CLR there is a flurry of downvotes suddenly. Goes from 2 to -1. It's almost as if there's someone at MSFT saying "look at this shit" to their colleagues in the office.

Sorry but this was a monumental piece of shit that took us out in production numerous times on classic .Net framework/CLR and I couldn't even get through to someone who gave a shit despite being a gold partner at the time and raising it on Connect. On Core, standard practice is to work around it because any time you open a ticket it gets autoclosed or ignored or just steamrolled (like the telemetry tickets)

I have no choice but to look elsewhere because I know any concerns I raise are ignored. MSFT dug this grave. The company is still the sick old dog it always was. Just a new shiny gown.

Wow do I hate this sort of shallow cynicism... Let me guess: companies are always screwing the customer, politicians are all corrupt, the media is always lying, etc.?

At least verify the testable facts you're relying before assuming bad faith!

The only redeeming quality of your inane comment is how neatly it proves my point.

Don't ever, ever, ever, ever... NEVER go to Reddit.

I'm losing more neurons than I am patience these days.

Reply on news.ycombinator.com