Software Engineering Daily · Software Engineering Daily

FreeBSD with John Baldwin

March 31, 2026·1 hr 4 min·5 clips

Netflix moved TLS encryption into the kernel to serve encrypted video to millions without crashing.

John Baldwin, a FreeBSD developer for over 25 years, joins host Gregor Vann to explore the history, governance, and modern applications of this foundational open-source operating system. The episode traces FreeBSD's origins from the Berkeley Software Distribution and examines its distinct path alongside Linux. Baldwin shares his personal journey from university sysadmin to a career centered on FreeBSD, working on projects ranging from TV broadcast systems to high-performance networking. FreeBSD began in the mid-1990s when a community split from the 386BSD project, building upon code released by UC Berkeley. An early lawsuit between AT&T and a company called BSDi created legal uncertainty that Baldwin believes shifted developer mindshare toward Linux at a critical time. The project's governance evolved from an initial "core team" to an elected board, a structure designed to outlast any single individual. Technical direction often emerges from developers "scratching an itch," whether for an employer or a personal project, with an estimated 80% of kernel commits being sponsored work. The PlayStation 4 uses FreeBSD partly due to its BSD license, which avoided complexities associated with GPLv3. Sony's contributions also helped FreeBSD adopt the LLVM/Clang toolchain. Netflix employs FreeBSD in its content delivery network to serve encrypted video streams efficiently. A key technical challenge was encrypting traffic without sacrificing performance, leading to the development of in-kernel TLS. This work was later extended to support Chelsio smart NICs that handle encryption directly, reducing memory and CPU overhead. Baldwin notes that technology choices like Sony's or Netflix's often stem from an engineer's familiarity or a specific technical need rather than a formal evaluation. The FreeBSD project is considering developing a more formal roadmap to guide volunteers, acknowledging that committee-based governance can sometimes lack efficiency. The operating system's integrated model, combining kernel, utilities, and a ports system, differs from the more fragmented Linux ecosystem. Baldwin reflects on the privilege of building a career around a project many treat as a hobby. The conversation is technical and educational, grounded in Baldwin's deep, firsthand experience. The host facilitates a clear chronological exploration, from historical context to contemporary use cases. Listeners interested in operating system history, open-source governance, or high-performance networking will find this episode compelling. Those seeking debates on current tech trends or beginner-friendly programming tutorials might find the deep technical focus less engaging.

As heard by us

A grounded look at FreeBSD's staying power, with real infrastructure stories and enough context to make the history land.

FreeBSD's staying power is the point here. John Baldwin and Gregor Vann walk through how a Berkeley-born operating system became quiet infrastructure, with the focus on engineering choices that kept it useful: governance, kernel scalability, storage work, and the discipline…

Read the full review in PlayNext →

Why you'd press play

You want the FreeBSD story behind Netflix's CDN and decades of steady engineering.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from Software Engineering Daily