composefs

eak many software systems, but a program that can reuse the world rather than being the world with it feels much kinder to me. with containers, typically this static binary question is less relevant, since the container has typically brought the world with it anyways, in most extreme form. However there's work like Composefs, which uses a content addressed store of blobs and a separate metadata layer to serve images, such that if multiple containers have the same (bit wise) file, they'll share the same content blob (including in the page cache). Less memory pressure, faster load times, all sorts of neat benefits from sharing the world. https://github.com/composefs/composefs https://github.com/containers/composefs-rs My hope is one day wasm can truly embody this spirit too, of a shared world, where small programs can have their dependency libraries satisfied by already loaded ready to go libraries. Allowing for very very start up and execution of programs that need even very sizable dependency trees, with little overhead.

ectory). Given it's use in awesome works like composefs for next-gen & content-addressed based container overlay type systems, this is a nice win. https://github.com/composefs/composefs Probably my favorite new feature is AMDGPU user queue (userq) work. Rather than the driver having to build out all the future work, now userspace can directly build the work of stuff to be done, sprinkling in various fences and what not. Some very interesting potential for GPGPU & perhaps ML! https://www.phoronix.com/news/Mesa-25.2-High-Priority-USERQ https://www.phoronix.com/news/Linux-6.16-AMDGPU-User-Queues The Kernel Newbies release log is one of my favorite things to read through. It wasn't bursting-at-the-seams with awesome as you sometimes get with releases, but 6.16 was still very fun. https://news.ycombinator.com/item?id=44717122 https://kernelnewbies.org/Linux_6.16