Reseña del libro "Integrated by Design (en Inglés)"
Modern infrastructure runs on Linux, and most engineers have never used anything else. Linux is not a system, though: it is a hundred sovereign projects stitched together by distributions. The seams are visible if you know where to look. Boot environments arrive in mainstream Linux a decade after FreeBSD shipped them. Container orchestration grows into platforms more complex than the workloads they were meant to run. Firewalls split into iptables, then nftables, then ufw, then firewalld, then back. Each tool, in isolation, is competent. The cost compounds in the integration tax that no one quite accounts for, and that everyone keeps paying.Integrated by Design sets a different example next to it. FreeBSD has been one system since 1993: kernel, userland, bootloader, and documentation maintained by one team, in one repository, under one set of conventions. The result is a platform that does fewer things on paper and more of them in practice. Boot a system into a snapshot of last Tuesday because last night's upgrade went wrong. Replace a firewall ruleset that fits on one page. Run a hundred jails on a laptop without orchestration software. None of this is exotic; it is what an integrated system looks like when nobody has to glue it together.Across twenty-two chapters, the book takes a problem (containers, storage, firewalls, package management, init, networking, documentation, server installation, virtualisation, the upgrade path that doesn't break) and shows the Linux solution next to the FreeBSD solution. The reader is not told which is better. The pattern speaks for itself.Written in BBC English with a measured, evidence-first voice. The reader is treated as an experienced colleague: shown the working terminal sessions, the configuration files, the structural decisions and their consequences. Not a polemic, not a marketing brochure. A working comparison, with the receipts.For Linux administrators who suspect there might be another way. For systems engineers tired of the next layer of orchestration. For anyone who has spent an evening debugging a boot loader that no single team owns.
