I gave it the old college try a few years ago out of some weird retro desire to use something "cool" like when I first found Linux in the late '90s. It was an obnoxious hassle nearly every step of the way, but I stuck with it as long as I could stomach. I did what felt like some pretty substantial work trying to update a port, and my issue just sat with no responses for months until someone else came along and independently re-did the work for a newer release.
The running joke about Linux is that next year is perennially the "year of the Linux desktop", but by comparison, FreeBSD feels like it's a decade away from achieving that kind of maturity outside of the server/middlebox space.
It is really difficult to suggest or even use a BSD myself. The hardware support is years behind Linux; Linux is often a year or behind Windows for new hardware, but much more for more niche things. Linux drivers, at least Intel and AMD graphics drivers, do tend to mature faster than their Windows counterparts in my limited experience.
Then you go into development work where the GNU version of many command line tools have more features than the BSD counterparts. Systemd offers very nice unification of a lot of previous disarrayed scripts. Wayland is the future, wish it was smoother and more unified, but people should not be using Xorg as it just does not handle things that well, such as different refresh rate monitors or screen tearing.
The only orgs that tend to use BSD tend to not want to give back. This harms the community. The GPL was very important for establishing a somewhat sustainable open source ecosystem.
> The only orgs that tend to use BSD tend to not want to give back.
This isn't true. Looking at the last year of git commits I see significant contributions from a large number BSD-using companies and organizations. Looking at the top of the list (roughly sorted by commit count) we have:
The FreeBSD Foundation
Netflix
Rubicon Communications, LLC ("Netgate")
Klara, Inc
Juniper Networks, Inc.
Beckhoff Automation GmbH & Co. KG
NVIDIA Networking
Chelsio Communications
DARPA
AFRL
NetApp, Inc.
Arm Ltd
Axcient
Microsoft
Intel Corporation
Amazon, Inc.
vStack
UKRI
Innovate UK
Stormshield
Modirum MDPay
iXsystems, Inc
Instituto de Pesquisas Eldorado (eldorado.org.br)
Citrix Systems R&D
Dell EMC Isilon
There are a couple of (admittedly high-profile) companies that use FreeBSD in their proprietary products with limited contribution to the community, but they are very much in the minority.
NetBSD runs on basically anything. They even fully support the Sega Dreamcast in the year 2023, and has great drivers support in the kernel. If you meant the latest and greatest niche GPU drivers, then sure your point stands.
> The only orgs that tend to use BSD tend to not want to give back
The single largest install of NetBSD is by SDF.org who absolutely gives back to the NetBSD community.
Supporting the Dreamcast is cool... if I wanted to do my computing on a Dreamcast, and if I wanted to do something like that for some reason it would make more sense to use a PS2 instead since it's the most popular console ever, but that has PS2Linux available already which has more software... so there's really no incentive to run BSD.
I'm willing to give a BSD a shot. But trying out OSes is so tiring now that I'm nearly 40. I really just want to pay for a working computer.
I recently was given an Apple computer for work, and I really loathe the whole experience. I'm completely spoiled by how flexible Linux is. You can make it do whatever you want. Apple seems hell bent on not letting you do anything, and what it does do is inefficient or clunky or just broken.
I would go back to Windows, but I keep hearing about how new versions are worse recently. And I expect it's a resource pig.
So before I switch away from Alpine (I finally got it working mostly well; but I have to be extremely careful before installing any package, because it likes to brick itself by removing packages like the wifi support), I'll give BSD a shot. But I anticipate hardware problems and maybe software problems too.
Surprisingly I had almost no issue setting up and Open Indiana machine. But while I do see the arguments for BSD on the server, for desktop it doesn't appeal to me. Requirements for desktop just include to many random third party apps and drivers.
> I'm still trying to make the full time switch to Linux
Just did that this year. After trying and failing every year I tried ubuntu + gnome + firefox, I succeeded by altering my choices: arch + hyperland + edge
I get the familiar pacman (used in MSYS2) and an UI that very closely matches my keyboard centric AHK configuration (no window borders, my most important apps run in fullscreen on their own workspace) in browser I'm used to (with my vertical tabs and groups, bookmarks etc).
I was using W11 Pro or Workstations before (so I didn't feel the pain home users have with disabled options or ads) and I loved windows, but the shady moves toward deprecating Office 2010 made me take a side as Excel is more important than windows to me.
Now Excel runs happily on Wine within wayland thanks to the HiDPI hyprland patches, I have a quaketerm very similar to Windows Terminal, and a sixel enabled terminal (wezterm) that's just as good as mintty for what matters to me (sixels, colors, italics, ligatures)
I still have some pains as moving to a different OS takes a lot of tweaks, but so far I'm loving it!
I would consider BSD for the native zfs support, but the lack of Bluetooth or SystemD and the pains to get modern options like Wayland means I won't.
It was removed from my start menu without me doing anything.
Also Microsoft has started deploying a special KB to figure out who's still using 2010, and there have been rumors it would get blocked in the future through another KB, even if it can run perfectly fine right now in Windows 11 as it did in Windows 10.
I like Office 2010: it's faster to start Word 2010 that even wordpad, so it's not a risk I'm willing to take. My bet on Linux (and wine to run Office 2010) has paid in spades.
I read something a few days ago how some developer at Microsoft had to explain why something wouldn't work on Windows for their OS designers who where all using Macbooks.
I can't think of any reason why would one use BSD on desktop or anywhere really.
BSD flavours were popular 10-20 years ago for licensing reasons. Think like Junos 9 (FreeBSD), FTOS (NetBSD).
Now the world largely moved to Linux.
OpenBSD is the most hassle free personal computing experience I can think of. My (now outdated, maybe) experiences with Linux involved:
1. Installing a user-friendly distro and scraping layer after layer of cruft off it until it finally performed acceptably.
2. Installing a cool minimalist distro and spending hours pasting commands from a wiki to build a brittle rice rocket OS that would explode if I sneezed at it.
I was shocked by how little configuration OpenBSD required in comparison. I always assumed it was some Gentoo tier wank given its elitist reputation. All the defaults were sensible. I just installed my favorite packages and went about life.
That brittleness aspect of minimal Linux setups is one of the reasons why when using Linux I just go with a full fat DE. It’s distracting and unproductive when it feels like your desktop setup is built upon glass stilts as a result of being so duct-taped together.
Yeah - generally speaking these days if I'm setting up a "desktop" running Linux it 99% likely going to be Kubuntu (with snapd purged and Firefox installed from the Mozilla Team PPA).
I have an Asus where the NVMe causes a BSOD every third startup or so.
Passes all the hardware diag I’ve done. No crashes for years using various Linux distros.
I lucked out this time. They (my wife and I bought two) were purchased in a panic when we had covid because we realized we did not have enough computers for the kids to do online school.
Linux is often the best tool for the job, but the BSDs have their place.
FreeBSD is a very good server OS. It supports ZFS and Dtrace right out of the box. Also it supports both binary packages via pkg and source based packages via the ports system. It also feels lighter on resources than typical Linux distros which is nice for older systems.
OpenBSD is an excellent router OS thanks to PF. It is more powerful than Linux for this purpose. Also the security track record for the default install is pretty much unrivaled.
NetBSD runs on a lot of obscure hardware that Linux doesn't support. It is the best tool for the job for reviving old otherwise unusable hardware. pkgsrc is also a very cool package management system that is not only supported on every architecture that NetBSD supports, but several other operating systems like Linux, macOS, and Solaris/OpenSolaris/Illumos/etc.
> FreeBSD is a very good server OS. It supports ZFS and Dtrace right out of the box.
zfs is easily achievable with Ubuntu. Dtrace isn't required by typical users.
> Also it supports both binary packages via pkg and source based packages via the ports system. It also feels lighter on resources than typical Linux distros which is nice for older systems.
Doesn't sound like any practical advantage at all.
> OpenBSD is an excellent router OS thanks to PF. It is more powerful than Linux for this purpose. Also the security track record for the default install is pretty much unrivaled.
PF is the only practical advantage of BSD over Linux but then again, unless you're running a router, you only need simple rules which can be done with any tools easily like ufw or even use cloud service control panel based ones.
> NetBSD runs on a lot of obscure hardware that Linux doesn't support. It is the best tool for the job for reviving old otherwise unusable hardware. pkgsrc is also a very cool package management system that is not only supported on every architecture that NetBSD supports, but several other operating systems like Linux, macOS, and Solaris/OpenSolaris/Illumos/etc.
Nothing practical.
On the other hand, not being able to run docker kills BSD's use by not being able to run any service easily hosted on docker hub.
And slight difference in CLI tools and shell behaviors kill all the little scripts you've written which makes it feel lazy to maintain scripts that work on both Linux and BSD. Quite hell of a job to maintain Ansible scripts that can create an identical environment on Linux and BSD.
"They said a Unix weenie was code for software engineers who hated what we were doing to Unix (the operating system we licensed)—putting a graphical user interface on it to dumb it down for grandmothers. They heckled Steve about his efforts to destroy it. His nightmare would be to speak to a crowd of them."
I use NetBSD to keep my sanity, but unfortunately, because of the sheer weight of the Linux userland, its resource inefficiency is slowly creeping into even NetBSD and OpenBSD.
Examples of feature creep? Sure. Rust is a good example. Anytime we deprecate a functioning C program with a Rust one, or add a Rust dependency somewhere, we also deprecate older hardware which can't cope with it, and make those machines useless.
Let's not even mention Electron, at least it won't work on NetBSD and OpenBSD, which prevents a lot of bloat.
Most Linux folks won't care about resource usage because they purposefully use powerful machines with gigs of memory, which hides inefficiencies.
NetBSD does the opposite, they purposefully test and develop the system on small, constrained hardware, whether new (ARM SBCs) or old (VAX stations, 486s and alike). But we can't fork the whole userland, so when Linux moves to large, bloated layers, it compromises a lot of efforts to keep the userland tight and fit.
Well, I also only use Desktop Linux via VMs, since Virtual Box and VMWare got good enough to run it, around 2010.
ChromeOS and Android don't really count, as the Linux kernel is the only thing from GNU/Linux being used for their desktop like purposes.
So in that regard, BSD and Linux are on the same boat anyway.
And as Steve Jobs used to point out, UNIX was never designed for the desktop anyway, note how NeXTSTEP and OS X developer stack barely care for UNIX workflows other than getting the UNIX (TM) stamp.
I don't know which BSD you are using but the article was regarding FreeBSD. One of the issues as noted in the article is the poor support for WiFi. FreeBSD doesn't support 802.11ac and support for 802.11n varies from driver to driver. Personally, being limited to 802.11g or 802.11n would be a nonstarter.
I have a FreeBSD vm running kde, but I don't remember if it's 12 or 13... it took a while to get the desktop running, but after that, it just felt like I was running Linux...
Is that a bad thing? I don't know. How come BSD doesn't have its own desktop? Or maybe it does and I didn't know about it at the time... but if I'm going to set up wayland I feel like I might as well run Linux.
Too bad, it's a chicken or egg issue. People won't use it unless it fits their needs. Have kept an eye on it for over two decades now, I still have an active FreeBSD installation but unfortunately, it's nowhere near usable as a desktop environment. In the meantime, Linux has improved a lot, and it's more or less ready.
Various issues, drivers, apps, updates etc.. I actually managed to get it working perfectly for me at some stage but a power outage ruined that. I probably still can get it working perfectly if I want to get down the rabbit hole. But unfortunately, I no longer have the energy to do so. I still do clean install every year or so to check how it goes, but you know, I no longer can spend weeks on just trying to get something working.
I’m using it, and I really like it. I’ve been using FreeBSD as my main operating system for more than two decades. Though I’m fairly OS agnostic, I keep a copy of Linux and Windows just in case. I accept its limitations(Bluetooth) and I think it’s great software
The way netbsd does drivers has always interested me. It seems like you could solve the problem with new distros not supporting lots of basic hardware by using netbsd’s drivers with your kernel
I gave FreeBSD a try a couple of years ago and it was a hassle all the way for me. It's not beginner friendly from what I remember but I hope that has changed.
The running joke about Linux is that next year is perennially the "year of the Linux desktop", but by comparison, FreeBSD feels like it's a decade away from achieving that kind of maturity outside of the server/middlebox space.