Why use static closures?

Why use static closures? (Published on March 3, 2026 - Version française)

F2R Articles
If anyone is interested, I released the crate on crates.io ​
https://crates.io/crates/gomi

Keep in mind it's still highly experimental but it's really promising. It should work in the majority of cases? I hope? If anyone wants to ̶b̶e̶ ̶m̶y̶ ̶g̶u̶i̶n̶e̶a̶ ̶p̶i̶g̶ give it a try, feedback is greatly appreciated.

#Rust #RustLang #GC #GarbageCollection #programming

RE: https://blahaj.zone/notes/aktwb5mkm25g00sw
Fuck you!
*Garbage collects your Rust* ​
#Rust #RustLang #GC #GarbageCollection #programming
Baby’s Second Garbage Collector

Implementation of the conservative garbage collector in lone lisp.

How to Catch the Memory Leak Hidden in Exception Tracebacks

Every caught exception secretly holds your entire call stack alive, leaking megabytes per request.

#python #memoryleak #exception #traceback #production #howto #garbagecollection #servercrash

https://www.youtube.com/watch?v=ZFYq-QJsEio

How to Catch the Memory Leak Hidden in Exception Tracebacks #exception

YouTube
How Ottawa’s changing garbage collection might affect you
The City of Ottawa has a new garbage collection contract that takes effect on March 30. It means new routes and schedule changes for about half the city. And as Arthur White-Crummey reports, for some it could mean a longer one-time transition period.
https://www.cbc.ca/player/play/9.7132465?cmp=rss

Dissecting the CPU-memory relationship in garbage collection (OpenJDK 26)

https://norlinder.nu/posts/GC-Cost-CPU-vs-Memory/

#HackerNews #Dissecting #CPU-memory #GarbageCollection #OpenJDK26 #CPU #Memory

Dissecting the CPU-Memory Relationship in Garbage Collection

Every time you configure a Java application’s heap size, you are essentially making a trade-off: spending more on infrastructure to improve performance metrics such as throughput or latency. Historically, this trade-off was visible when an undersized heap triggered long pauses, signaling a need for more resources. With modern collectors, however, pause duration and computational effort have become decoupled. This creates an operational blind spot: dashboards may show excellent response times, while the collector silently consumes excess compute capacity to compensate for a constrained heap. To address this, it is essential to look beyond GC pauses and examine overall efficiency using new tools. This article, therefore, analyzes why we need additional metrics for infrastructure efficiency and introduces the new Java API for GC CPU in OpenJDK 26, which empowers engineers and researchers to quantify the collector’s CPU overhead and make informed memory-CPU trade-off decisions.

Jonas Norlinder

As a reminder, it's good #OpSec regularly to purge any paedophiles from your #network.

#GarbageCollection

It’s About to Get a Lot Easier for Your JavaScript to Clean Up After Itself, by @Wilto (@piccalil.li):

https://piccalil.li/blog/its-about-to-get-a-lot-easier-for-your-javascript-to-clean-up-after-itself/

#javascript #garbagecollection

It’s about to get a lot easier for your JavaScript to clean up after itself

There’s some very useful capabilities coming to JavaScript: “[Symbol.dispose]()” and “using”. Mat Marquis is here to explain why they’re coming and how to use them effectively.

Piccalilli