News for hackers. Stuff that matters.
Re:I was wrong, reflecting on the .NET design choices by OniBait on Friday April 21, 2017 @07:23PM (#14170218)
You can use things like System.GC.TryStartNoGCRegion and GCLatencyMode.SustainedLowLatency to help mitigate the GC pauses though. There is a lot of work that has been going on with the CLR GC code somewhat recently.
Re:I was wrong, reflecting on the .NET design choices by psyc on Friday April 21, 2017 @08:11PM (#14170415)
What I want is no GC. I might settle for a way to tell it "Do not walk this graph over here, ever, ever." But really, I want to be nowhere near a GC at all, unless it gives me control of pretty much everything it does. I do develop in C#, and I have to work around the GC every step of the way. I really want not to have to work around it, not better work-arounds. For the most part, I simply don't allocate, but that is ugly and non-idiomatic.