> podman, unfortunately IMO, is also written in go. Podman, by default, uses crun as the container runtime, which is written completely in C. Podman is basically just a frontend for managing running containers.
The trap is already here for me. When I make a passkey for my corporate microsoft account, I'm only allowed to use Microsoft Authenticator on an approved device (it's not a work provided phone. Microsoft Authenticator…
hfsplus driver supports write for both journaled and non-journaled partitions, though it only mounts r/w by default for non-journaled partitions.
You can access an encrypted HFS+ partition from macOS and Linux machines natively. Very useful for sharing data between Asahi and macOS, and in general between Linux machines and macOS.
And how exactly did the BSD license make creating Valkey easier? GPL and BSD licenses both have the source in the open. Anyone creating a fork, can easily do so for either BSD or GPL licensed projects. Since Redis is a…
> podman, unfortunately IMO, is also written in go. Podman, by default, uses crun as the container runtime, which is written completely in C. Podman is basically just a frontend for managing running containers.
The trap is already here for me. When I make a passkey for my corporate microsoft account, I'm only allowed to use Microsoft Authenticator on an approved device (it's not a work provided phone. Microsoft Authenticator…
hfsplus driver supports write for both journaled and non-journaled partitions, though it only mounts r/w by default for non-journaled partitions.
You can access an encrypted HFS+ partition from macOS and Linux machines natively. Very useful for sharing data between Asahi and macOS, and in general between Linux machines and macOS.
And how exactly did the BSD license make creating Valkey easier? GPL and BSD licenses both have the source in the open. Anyone creating a fork, can easily do so for either BSD or GPL licensed projects. Since Redis is a…