https://wid-blog.github.io/en/tags/memory/Recent content in Memory on wid's blogHugoenFri, 14 Jun 2024 00:00:00 +0000https://wid-blog.github.io/en/posts/tech/language/three-garbage-collectors/Fri, 14 Jun 2024 00:00:00 +0000https://wid-blog.github.io/en/posts/tech/language/three-garbage-collectors/All three languages use a garbage collector, but the priorities differ. Java leans on generational + region GCs (G1, ZGC), Python combines reference counting with a cyclic detector, and Go runs a single concurrent tri-color mark-and-sweep. What each GC gave up is what shapes its operational profile.https://wid-blog.github.io/en/posts/tech/language/everything-is-pass-by-value/Thu, 13 Jun 2024 00:00:00 +0000https://wid-blog.github.io/en/posts/tech/language/everything-is-pass-by-value/Calling a function with an object is often described as pass by reference, but in memory all three languages copy values. Java copies a reference value, Python binds a new name to the same object (call by sharing), and Go copies a struct header — escape analysis decides where the values live.