Hacker News new | past | comments | ask | show | jobs | submit login

If you want a desktop, it may or may not be for you.

If you rely on VPSes, it may not be for your because your options for providers here are somewhat limited.

However, if you are running your own hardware for your own server, and you are of a sysadmin temperament that likes to know exactly what's going on (because you put it there), then FreeBSD is excellent. Stable, reliable, everything works like the Unix you wanted and signed up for.

I have several decades of experience working through the commandline, and that's how I prefer to do things. FreeBSD makes this a first-rate experience. And I have to say that the deep integration of ZFS on a server under your control is life-changing.

I use a Macbook for the everyday things, like making presentations or playing games or movies. It is by far the best experience, since everything just works. (A Windows machine may be the same for others, I just prefer MacOS.) So a Linux desktop has no particular value for me.

But if you want to keep a stable of servers, each running under your specific control, to the point you have a poudriere machine to provide specifically built packages for your herd of machines and a bevy of automation scripts to keep them under control, FreeBSD is certainly something to look at.




So let's focus on the case where I'm setting up a bunch of bare-metal hosts as servers. What's the value proposition of using FreeBSD over Debian/Ubuntu if we're not counting familarity?

Either experience will be CLI first, so this is a tie.

ZFS integration is one point. If that's important to you, then you'd want to pick a distro like Ubuntu with first-class support. All major development happens on the Linux on ZFS branch as far as I understand, so this should be okay.

As the original post points out, FreeBSD used to have unique features as selling points: zfs, dtrace, the network stack (before SMP became ubiquitous?), kqueue, jails. I'm sure there are others. But these days it seems Linux has caught up with developments like ebpf, cgroups, namespaces and io_uring.

I'm sure the fragmented nature of Linux means that some of these low-level techs are easier to use on FreeBSD. The counterpoint is that the higher-level stack is more well-supported on Linux. You may not have to care too much about the details of namespaces and cgroups if high-level docker/kubernetes/... tooling works for you.

What am I missing?


That's a great summary that details what I was suggesting.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: