The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)
1–10 of 64 posts
Re: The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)
#2I remember reading it before. My son threw it away when we moved houses, not knowing how important it was. I'd recommend it.
Re: The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)
#3I remember reading it before. My son threw it away when we moved houses, not knowing how important it was. I'd recommend it.
Ironic that this of all books got garbage collected prematurely.
Re: The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)
#4I remember reading it before. My son threw it away when we moved houses, not knowing how important it was. I'd recommend it.
Q: what kind of collection is this real world example illustrating?
A: Copying Garbage Collector (semi space). Chapter 4!
Great book. I was always fascinated by bakers treadmill. Always wanted a real world case where I could implement one with Fibonacci sized mills.
Re: The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)
#5How good are AIs at coding manual memory management? Is this a sea change in automatic memory management?
Re: The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)
#6What I didn’t like about this series of books was choosing “garbage collection” as umbrella term for both tracing GC and reference counting, without verifying if programming community would agree with that, which turned out they didn’t.
I’ve seen a lot of threads here and on reddit where people were arguing about terminology purely because of this book alone.
By that definition, C++ code has garbage collection if it uses std::shared_ptr, going against widespread common usage of the term “garbage collected programming language” which specifically contrasts manual languages like C++ or Rust against garbage collected ones.
“Automatic Memory Management” is a lot more suitable description to what programmers have to do to manage memory; it is now in the title but still hasn’t become the primary term.
Re: The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)
#7What I didn’t like about this series of books was choosing “garbage collection” as umbrella term for both tracing GC and reference counting, without verifying if programming community would agree with that, which turned out they didn’t. I’ve seen a lot of threads here and on reddit where people were arguing about terminology purely because of this book alone. By that definition, C++ code has garbage collection if it…
The Linux kernel has garbage collection, and not just the controversial refcount kind.
Re: The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)
#8I had the 2012 print edition. One of the best books available - the best book that I knew - about GC at that time.
Anti-pattern: Regarding the 2023 e-book edition, I do not see a way to buy it from the site, or even a link to buy.
Re: The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)
#9How good are AIs at coding manual memory management? Is this a sea change in automatic memory management?
I have never seen Codex or Claude get manual memory management wrong. I used to be pretty fastidious about using leak sanitizer or other such tools to catch my own memory management issues, and while not quite useless, that sort of testing has dropped way down my list of worries the more I lean on LLMs. I am constantly surprised by how many formerly tedious or error prone tasks stopped being either of those, and I expect to see practice shift away from middle-safe languages like C++ to not just much more safe languages like Rust but surprisingly also to much less safe ones like C and platform specific assembly.
Re: The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)
#10[flagged]