Linux everywhere

A Blax engineer's laptop runs Linux. Their IDE runs on Linux. Their shell is the same shell that is on the server you will deploy to. The file paths, the package manager, the signals, the way a process pins a CPU core: identical at every step. When a bug only reproduces in production, it is rarely "production has a different OS"; it is something specific, and we find it faster because the OS itself is not part of the mystery.

Production incidents tend to surface at the worst hours. The engineer answering the phone on a Friday at 2am does not have time to learn the OS that night. They are using it, on their laptop, the same way they will use it on the rack. Same diagnostics, same logging conventions, same shell muscle memory. Linux familiarity is part of the incident-response kit, not something you pick up the moment you need it.

Linux is the substrate underneath every other conviction we have. Docker only makes sense because Linux gave us namespaces and cgroups. Open source by default only works because Linux IS open source. Our WebSocket runtime picks the same event-loop primitives the kernel exposes. Each one of these is cheaper, more reliable, and more debuggable because the underlying OS is the same boring, ubiquitous thing.

Internally we mix Fedora, Ubuntu, NixOS and Raspbian depending on the job, and our production hosts are usually whatever the customer's team is comfortable maintaining. The point is not the distribution. The point is that "Linux" is the family we live inside, the same way a wood-shop lives inside "wood" without making a religion of which oak they bought this month. Pick what works for you; we deliver in it.

A Linux-native team picks the right tools the first time. Cron, systemd, iptables, ssh, fail2ban, journalctl, the standard libc, the standard process model: these are not bespoke skills for us, they are how we already work. Your project does not pay an "OS learning curve" tax. You also avoid the soft-but-real costs of a stack that grew up on macOS and gets surprised by case sensitivity, gets confused by symlinks, or forgets that production does not have Homebrew.