News for hackers. Stuff that matters.
Re:Generics can make your Go code slower by zinekeller on Wednesday March 30, 2022 @07:08PM (#30861973)
> I've never had to debug corrupted memory

You're lucky! When OpenJDK was still closed-sourced Hotspot from Sun, we have chased bugs that Sun confirmed was a defect on how Hotspot handle memory (and this is on a ECC'd system of course), although these days I can't remind of anything remotely related.

> or how a use after free bug let people exfiltrate data.

Technically you're just outsourcing it :)

Re:Generics can make your Go code slower by EdwardDiego on Wednesday March 30, 2022 @10:31PM (#30863243)
Yeah, have only ever hit one or two JVM bugs in very rare circumstances - which we usually fixed by upgrading.

> Technically you're just outsourcing it :)

Haha, very true. Luckily, to developers who are far better at that stuff than the average bear.

The recent log4j rigmarole is a great example of what I was describing in JVM dev though - no complicated memory issues involved, definitely not GC related, just developers making decisions using technologies that had very subtle footguns they didn't understand (the capacity to load arbitrary code via LDAP was, AFAIK, very poorly known, if not forgotten, until Log4Shell).

Re:Generics can make your Go code slower by Karrot_Kream on Wednesday March 30, 2022 @08:13PM (#30862389)
> You're lucky! When OpenJDK was still closed-sourced Hotspot from Sun, we have chased bugs that Sun confirmed was a defect on how Hotspot handle memory (and this is on a ECC'd system of course), although these days I can't remind of anything remotely related.

I mean sure. I remember having similar issues with early (< 2.3) Python builds as well. But in the last decade of my career, only a handful of outages were caused by Java GC issues. Most of them happened for a myriad of other architectural reasons.