pleroma.debian.social

Apparently there's a term for people like me: Never Nester.

"Why You Shouldn't Nest Your Code"
https://youtube.com/watch?v=CFRhGnuXG-4&si=BoEfFqgNsOwV7ez5

… expose these kinds of deps really nicely in their packaging metadata, if they just knew about them.

Hence, if the lack of dep metadata is the main big con of dlopen() deps, let's see if we can do something about it!

here's my proposal about this: https://github.com/systemd/systemd/pull/32234

It's a very simple approach. All it does is insert an ELF "note" into generated binaries that declare these deps. This information can then be consumed by package managers, initrd generators and other tools.

Every internet of shit, phone, tablet, and other sorts of device manufacturers should be required to push/post a root unlock firmware for their devices before they can stop supporting them. There's too goddamn much ewaste from everything already. If they're going to abandon their devices, at least make it easy for people to unlock them and do whatever else they want with them.

“a compiler is when the dependency hell happens on the developer's computer, and an interpreter is when the dependency hell happens on the deployment target” - ohAitch

My number one wish from the fallout of the xz backdoor is that it kills autoconf/configure/autohell. That shit is illegible and watching for compile failure is a shitty way to test for features

💚 Stay strong xz maintainer(s). We're with you.💚

#scrum #priorities #leadership #sprintplanning #Meme #memes