git was created because a proprietary VCS was being a dick

I assume that’s how SCP-3008 was created

https://scp-wiki.wikidot.com/scp-3008

Ironic timing https://christianselig.com/2024/10/juno-removed/

Both GNU and GrapheneOS have staunch requirements and will accept no compromises.

This is a situation where their requirements don’t align, so they’ll never reach an agreement.

GrapheneOS, for example, is also strictly against making the Fairphone line of phones a little more secure because it doesn’t meet all of their security requirements

In this case GNU won’t certify GrapheneOS as fully open because it includes binaries that aren’t open

The FSF is more along your line of improving the situation where they can

Well, a.out doesn’t make much sense these days.

Gotta move to .elf

It looks like an alternative to LocalSend rather than Syncthing

There was one on Reddit - I came to see if someone linked one

Yeah, that’s bizarre. I’d never have guessed /home was created by tmpfiles

The one they use at my work is extra silly, as it adds an extra email header saying it’s coming from a phishing campaign

There’s assembly and makefiles too

Less of a joke answer, there has been work to allow Rust bindings for drivers.

At a high level, microkernels push as much as possible into userspace, and monolithic kernels keep drivers in kernel space

There are arguments for each e.g. a buggy driver can’t write into the memory space of another driver as easily in a micro kernel, however it’s running in the same security level as userspace code. People will make arguments for both sides of which is more secure

Monolithic kernels also tended to be more performant at the time, as you didn’t have to context switch between ring 0 and ring 1 in the CPU to perform driver calls - we also regularly share memory directly between drivers

These days pretty much all kernels have moved to a hybrid kernel, as neither a truly monolithic kernel nor a truly micro kernel works outside of theoretical debates