Darwin (macOS, iOS, iPadOS, tvOS, watchOS)?
And I guess that technically Minix is one of the most successful Unix-like systems. [1]
Those are systems for Apple to control you and their devices that you paid for, not for you to control any device that you own. Therefore, the only traction they've really gotten is with one single user - Apple.
> macOS
For now.
(Relax everybody, I'm at least half kidding.)
You can't change much about how MacOS works under the hood anymore. If you don't like how it works, tough.
The device and OS are not yours.
Also why no one could pay me enough to rely on Apple hardware or software at this point for anything but entertainment.
On top of that, the unix userland resembles FreeBSD, although it's pretty eclectic in choices, e.g. it ships with GNU grep and GNU make by default IIRC while I think FreeBSD uses BSD grep and make by default?
(Darwin is pretty eclectic overall -- some portions are more NetBSDish. Kernel is mostly Free I think)
IME, most of the basic shell commands are either directly from FreeBSD or a project in the BSD universe. For example tar is from libarchive, a distinct project (see https://github.com/libarchive/libarchive) that DragonflyBSD, FreeBSD, NetBSD, and macOS import and track. (But oddly not OpenBSD, which has evolved the 4.4BSD-Lite implementation.)
According to a 2012 accounting at http://meta.ath0.com/2012/02/05/apples-great-gpl-purge/ (via https://news.ycombinator.com/item?id=3559990), macOS was down to 16 GPL packages in macOS 10.12 from 47 in macOS 10.5.
Yep, it still is. On Big Sur on M1:
$ grep --version
grep (BSD grep) 2.5.1-FreeBSDOn the other hand, it looks like (at least on Catalina?) it ships with GNU diffutils, so patch, cmp, diff are all GNU utilities. I'm going to sheepishly pretend like this proves my point somehow :-)
FreeBSD should be able to switch before 13.0, but the bsdgrep developer is a slacker. It's only missing a couple of GNU extensions that are somewhat surprisingly (to me) common.
I would guess that there are more BSD users than there ever have been in 2020.
FreeBSD (like *BSD in general) may be a niche OS, but there are probably millions of users and thousands of developers; certainly enough to keep the platform going.
Not everything has to be mainstream, after all; there is probably a "medium tail" of operating systems which BSD is a solid part of.
If Linux never happened, we would still all be using HP-UX, Solaris, Aix, Tru64, and all the other clones that integrated some form of BSD code.
> If 386BSD had been available when I started on Linux, Linux would probably never had happened.
This depends on the use case of the company.
A lot of companies learned that simply forking the project and not giving back is a good pathway to pain because now you have to carry your internal patches forward, as well as a larger and larger diff against the base OS itself as it changes.
If you forked (e.g.) FreeBSD 9 and based your product off of it, and the project is now at version 12.x (with 13.x in 2021Q1), then that's a lot to keep up with internally.
It's better to use the base OS, and the documented APIs, for one's secret sauce, and give back everything else. This is what vendors like Netflix, Dell-EMC Isilon, NetApp, etc. do. You'll also see quite a few patches from Microsoft and Amazon as they want to sell their cloud services for as many guest OSes as possible. Hardware vendors (Chelsio, Mellanox, Cavium) also throw in support so that hardware companies will use their products with-in appliances.
Others, like Sony with the PS4 and PS5, mostly seem to operate in user land and so do not do much kernel-level stuff (except perhaps booting code) that would need to be back ported.
If FreeBSD (or Linux) weren't around, then they'd simply purchase/license an embedded OS (QNX?) and use that.
There is hardly a reason to install them other than wanting free beer OS without GPL-strings attached or being a systemd hater, and then suffer a desktop experiece that feels like stuck in early 2000.
Conferences related to BSDs usually boil down to running the same code in newer hardware or filesystems.
You know why you never seen a Google Server OS? Because you just have to give code back to the community if you REDISTRIBUTE your code.
>Conferences related to BSDs usually boil down to running the same code in newer hardware or filesystems.
That's complete and utter BS, you really sound like a hater but not a systemd one.