With that said, I use FreeBSD for my home server and also inside VMs, but I find myself using Linux more. There are many situations where I often need to use Linux instead of FreeBSD due to either software compatibility reasons or lack of drivers.
I almost made the switch to FreeBSD a few times but Slackware still offers fewer compromises for me with the same ridiculously stable user experience and I don't have to worry as much about drivers when computer shopping. I assume I will end up switching to FreeBSD when Patrick dies since Slackware will probably die with him so I keep an eye on it and play with it once every year or two.
The vid talks about how big Linux vendor, like Red Hat, betrayed the Linux community (their words, not mine).
If you're fine with the "microsoftization" of Linux, then you're all good and set with Fedora or Ubuntu.
For many users Linux is just "Windows but sucking a bit less than Windows".
But others do feel the betrayal they talk about in the vid. For me for example systemd and systemd's author now officially being on Microsoft' payroll is a very hard pill to swallow. Same for many non-portable things now targeting only the bastardized Linux ecosystem, instead of targeting all the Unixes still out there (including FreeBSD and OpenBSD).
Thankfully due to the unfathomably big number of Linux containers / virtual machines being spun on and off and the need for utmost speed of these, systemd ain't much of a thing in the Linux container world. And Linux is still the kernel and it's still possible to have both systemd-less containers and systemd-less distros. I'm not sure how long that'll last though seen how systemd is spreading its tentacles everywhere.
For people who love Microsoft INI files and who love the rube-goldberg monstrosity that Windows is, systemd Linux distros with snap and whatnots are just fine. To them Linux is just basically a Windows a tiny bit more secure and crashing a tiny bit less. And don't worry: Microsoft employees are hard at work making sure Linux gets shittier by the day, emulating the mistakes of the biggest turd of an OS ever made (that'd be Windows).
For others, thankfully the BSDs do still exists.
What I personally really like about the BSDs are that they are very hackable with great documentation. The code base is much smaller and building your own kernel is very straightforward. I was able to even fix some of my own drivers and learnt a ton in the process.
Started[0] by NetBSDs (and Hacker News') own jmmv[1]. So if you're getting BSD vibes, now you know why.
I don't use BSD, but as a long time user of Linux (started with Yggdrasil) I can't help but think Linux is slowly but surely getting sabotaged. Systemd, Wayland, Pulseaudio, it is all needlessly complicated and introduces dependencies in other software that shouldn't be there.
Maybe I _should_ take a good look at the BSD's after all.
Hardware support is abysmal though.
Yes.
Firefox may work better on FreeBSD, or not -- I don't have as much personal experience with it. (It's not like there are a huge number of BSD Firefox developers, either.)
Can you help me? I didn't find any in that article. Maybe I missed in the flood of term 'market share'.
What about desktop environments though? I always thought KDE and GNOME were first class citizens on FreeBSD.
I hope that the Linux community will long retain at least some echo of that exploratory spirit, and extend that to projects like FreeBSD.
In that exploratory spirit, I ran FreeBSD for years. It has a number of every-day shortcomings compared to Linux. If Linux users want to be annoyed and inconvenienced regularly in the spirit of exploration, sure, they can give it a shot.
It is 2024. I do not care about the browser functionality for ~15 years.
That was back before systemd/wayland, and back when deleting pulseaudio just made everything work better.
Also, minimal window managers like evilwm were more tenable, since the only useful thing that really used the notification area/dbus was wifi.
Anyway, being behind on the spiral of instability I’ve seen with recent Linux desktop environments seems like a feature, not a bug.
For me being "behind on features and tool versions" actually means that there's much less going on so I'm more confident that everything works and works well together. From my POV Linux has developed a case of Winchester Mystery House syndrome.
I run both Arch Linux and FreeBSD. It is not uncommon that FreeBSD's packages update faster than Arch Linux. Make sure you update your pkg config to use the latest packages instead of the quarterly packages it uses by default.
Also, I'd like to point out that FreeBSD has thousands of more packages than Fedora: https://repology.org/repositories/statistics/newest
> why would I consider FreeBSD
ZFS: Since FreeBSD isn't encumbered by the GPL, it has fully integrated ZFS which is a far better experience than on Linux. On FreeBSD ZFS always works, whereas on Linux ZFS is an out-of-tree module and your dkms builds breaks frequently when the kernel updates. Also, a lot of software on FreeBSD takes advantage of the features of ZFS, whereas on Linux most software doesn't use the features of either btrfs or ZFS.
PF: This firewall has a great config format. After using PF, Linux's iptables makes me want to walk into the ocean.
poudriere: A great and easy-to-use package builder. I use this to build both my OS and all my software with CPU optimizations for my specific processor (but FreeBSD has official package repositories, so you don't need to build your own if you don't want to.)
kqueue: FreeBSD uses the kqeueue syscall. Later Linux created their own syscall: epoll. But epoll is fundamentally broken: https://idea.popcount.org/2017-02-20-epoll-is-fundamentally-...
jails: more secure than Linux containers despite being invented 7 years earlier.
sysctl instead of /proc: On FreeBSD, when you're listing the running processes (for example, top, htop, or ps), it uses sysctl which gets an atomic snapshot of the running processes. On Linux, you have to crawl through the /proc filesystem which is MANY more syscalls and the contents of /proc are changing out from under you while you're crawling through it.
-----
That being said, Linux has some wins over FreeBSD:
systemd: As controversial as it is, I think systemd is nicer than FreeBSD's init system. systemd supports user services whereas the built-in FreeBSD service manager does not (3rd party ones do though). Systemd automatically captures stdout/stderr to a log whereas FreeBSD relies on each service invoking the daemon tool to redirect their stdout/stderr. FreeBSD still uses pidfiles for everything which is flawed.
documentation: FreeBSD has much better man pages than Linux, but the Arch Linux wiki is the champion, no contest.
wifi: FreeBSD's wifi support is definitely not great. There are efforts under way to make a shim that will allow FreeBSD to use the Linux wifi drivers (similar to what they did for graphics drivers) but where it stands today, the wifi support is not great. That being said, there is a package called "wifibox" that spins up a tiny Linux VM and has Linux drive your wifi card, bridging the connection back to FreeBSD.
------
Finally, this is a popular blog post on why someone would choose FreeBSD over Linux: <go see Vermaden's post at https://news.ycombinator.com/item?id=41820161 >
Edit: Vermaden himself has posted the link to his blog post at https://news.ycombinator.com/item?id=41820161 so I am removing the link.
Even ebpf is superior to dtrace.
It's not even a fair comparison because the world runs on linux, all the tech company heavily use Linux so there a vast amount of money poured into it.
As for ZFS I've been using it on Ubuntu on my NAS which is 10 years old with 0 issues, never had a single issue.
I disagree. FreeBSD has pf which is the superior firewall (as does OpenBSD and OSX). FreeBSD has jails which are the superior containers, and bhyve for virtualization (also ported to OSX as xhyve) which is wonderful because it doesn't support any sort of legacy devices like floppy disks which have lead to security vulns in qemu. In terms of security, since you used the term "BSD" I am going to include OpenBSD in this comparison, which is the obvious champion of security.
> As for ZFS I've been using it on Ubuntu on my NAS which is 10 years old with 0 issues, never had a single issue.
That's because Canonical decided to ignore the license issues and bundle ZFS with Linux. Every other distro honors the license: https://ubuntu.com/blog/zfs-licensing-and-linux
Well, I don't want to be that guy, but you're wrong about that too ;)