دانلود کتاب راهنمای جمع آوری زباله

This is the second edition of The Garbage Collection Handbook. How is it that, more than sixty years after the introduction of garbage collection in 1958 and exactly thirty years1 since the first International Workshop on Memory Management (the forerunner of the International Symposium on Memory Management) in 1992, garbage collection in particular and memory management more generally remain such vital topics of research and development? Garbage collection was born in the Lisp programming language. McCarthy [1978] recollects that the first online demonstration was to an MIT Industrial Liaison Symposium. It was important to make a good impression but, unfortunately, midway through the demonstration, the IBM 7042 exhausted (all of!) its 32k words of memory — McCarthy’s team had omitted to refresh the Lisp core image from a previous rehearsal — and its Flexowriter printed, at ten characters per second, THE GARBAGE COLLECTOR HAS BEEN CALLED. SOME INTERESTING STATISTICS ARE AS FOLLOWS: and so on at great length, taking all the time remaining for the demonstration. McCarthy and the audience collapsed in laughter. Over sixty years on now, garbage collection is no joke but an essential component of modern programming language implementations. Indeed, Rust (first released in 2012) and Visual Basic (introduced in 1991) are probably the only widely used languages developed since 1990 not to adopt automatic memory management of some kind, yet Rust provides a reference counted smart pointer and VB.NET (2002), a modern incarnation of Visual Basic, relies on the garbage collector in Microsoft’s Common Language Runtime. Garbage collection continues to be a vibrant area of research and is far from a solved problem. In Blackburn’s words [2022], “Seismic technology shifts, unprecedented scale, concerns for energy efficiency and security, a diversity of programming languages and above all, ubiquity, have conspired to make memory management more challenging, interesting, and important than ever.” Memory management sits at the crucial interface between the hardware and the programming language. It presents deep problems and challenges, both theoretical and engineering. Garbage collection is probably more important and affects more people than ever before. It is in their phones and their browsers; it is in the servers in the cloud on which so much of modern life depends. Despite the growth in capacity on every device from the smallest one in your pocket to the largest systems in enterprise-scale warehouses, memory is not free and efficient access is vital. For example, recently Hunter et al. [2021] found (and then recovered) 26% of memory that was wasted due to fragmentation in Google’s warehousescale computers: a significant cost in both financial and energy terms.