throwaway127482

You're describing ASI, not AGI.

They did some interesting wordsmithing here to cover their ass without saying it directly.

See, this is what happens when you turn off thinking completely.

How is it more helpful for debugging compared to just looking at the git patch? As far as I can tell, this is meant to be more of a cool presentation type thing, rather than something to assist with development

Not a realistic solution at all

I think you're misunderstanding. If you have an extremely large number like 2^256 you will almost certainly never find two people with the same birthday (this is why a SHA256 collision has never been found). That's what the top-level comment was comparing this to.

This was covered in my computer architecture class, which was mandatory for my CS degree.

Conspiracy theory: that explanation is a lie, and the real reason for the delay is that it helps hide the fact that there isn't a unique image mapped to each pixel. If you click two pixels very close together, it shows the same image, but slightly shifted to exactly match your pointer. If the images were displayed immediately, it would be much more obvious what's going on.

Completely and utterly off topic: why on earth does HN use a dim gray font for the post description? It's so hard to read. I understand why downvoted comments are grayed out but why the post description???

Correct. And we know the AI will read the docs whereas people usually ignore 99% of docs so it just feels like a bad use of time sometimes, unfortunately.

I love spreadsheets and use them a ton but I have to agree, creating charts is hard

Getting a 404 from that link

With data intensive Go applications you eventually hit a point where your code has performance bottlenecks that you cannot fix without either requiring insane levels of knowledge on how Go works under the hood, or using CGo and incurring a high cost for each CGo call (last I heard it was something like 90ns), at which point you find yourself regretting you didn't write the program in Rust. If GC in Rust could be made ergonomic enough, I think it could be a better default choice than Go for writing a compiled app with high velocity. You could start off with an ergonomic GC style of Rust, then later drop into manual mode wherever you need performance.

cgroups aren't relevant here, I think. Not sure if that was just a typo, since you did mention namespaces in the first sentence. PID and user namespaces in particular are relevant here.