when you regret open sourcing Java because eventually your daughter has to learn it
@RadicalEdward hah, love this. I once sat next to a woman on a plane who looked over and said something along the lines of "do you mind if I ask why you're writing Go instead of Java?" and I said that I'd wasted years of my life trying to tweak the million settings to make the Java garbage collector behave and she replied "oh, I wrote that". I both felt slightly bad for being rude, and was also mad at her for the hell she put me through. For the rest of the flight we sat in stony silence.
@sam @RadicalEdward That may be the best airplane story I have ever heard
@sam @RadicalEdward lol, if you are angry about the Go garbage collector now, I know the person that wrote that too.
@irene @RadicalEdward I've never had a problem with that one, it's mostly just been good enough, maybe with the occasional long pause while under heavy load that had to be worked around. If it's complaints about Go you want though, I'll gripe about the strict control the Go team maintains over the language and how much I hate the proxy and packaging systems all day :)
@irene @RadicalEdward (I used to know a lot of people on the Go team as well, no idea if any of them are still there though, it's been years since I contributed at all and I mostly just try to avoid interfacing with Google as much as possible these days)
@sam @RadicalEdward yes, I told Austin (the person that wrote the garbage collector) that Go was like a dictatorship and Rust is anarchy.
@sam @RadicalEdward I worked with some developers who had to maintain that collector. They used terms like "floating garbage" to describe parts that didn't work too well. IIRC it wasn't type accurate so you could get false positives when marking.
@sam @RadicalEdward Oh yes, I remember now. The same team used to call "finalizer" the "f-word", because of the possibility of a finalizer making an apparently dead object live again. The uncertainty of when a finalizer runs was an extra complication.