5 ms·
I'd like that as well, but my suspicion is that Linux is now "good enough" via things like io_uring that a highly visible comeback for *BSD is less likely.
by tyingq 6y ago
I'd like that as well, but my suspicion is that Linux is now "good enough" via things like io_uring that a highly visible comeback for *BSD is less likely.
- nix23 6y agoTo be honest, Linux is also not highly visible, sure for the HN-Community it is. But for normal Customers? They know Android, Windows, MacOS..that's it.
- tyingq 6y agoI had assumed "comeback" meant in the backend server space.
- tutfbhuf 6y agoWell Android is a Linux distro with a kernel patchset for smartphones.
- bch 6y agoWell... tell somebody you run a Unix operating system instead of Windows or Mac and keep notes on how many people say “Oh, you mean Linux?” Keep a smaller piece of paper for all the combined responses of “Oh, you mean [Open|Free|Net|Dragon Fly]BSD?” I’d be surprised if you need that second piece of paper at all. Written as a satisfied NetBSD user.
- wolco2 6y agoI would actually think you run Unix and would never question them. If they know the word Unix they probably aren't confusing it with linux.
- nix23 6y agoHehe true, if they know whats Unix is, they ask probably MacOS, Solaris, Hp-UX, AIX, or OpenServer/Unixware...but for sure not Linux or any BSD.
- boogies 6y ago> Unix operating system instead of Windows or Mac macOS is a BSD, just buried under layers of proprietary UI, tracking, and DRM
- paulmd 6y agoThe draw for BSD is the BSD license - it is not a "copyleft" license, you do not have to redistribute source to those whom you provide with binaries. Same reason Intel chose MINIX over Linux for the Intel Management Engine. As such, Linux will never fully substitute for the use-cases that BSD provides. More or less - BSD focuses on developer freedoms while GPL focuses on end-user freedoms. GPL does not provide you the ability to redistribute binaries without source, while BSD does, so BSD is desirable where obscurity is an element of depth in defense (eg Sony's playstation OSs, Intel ME, etc), or where you simply don't want to redistribute your derivative code (MacOS X, etc). GPL also does not allow you to link GPL-incompatible code (either proprietary or non-compatible open-source licenses) that you don't own and can't relicense to GPL compatible, as that inherently locks off a significant amount of code that you might potentially need (what if you are licensing an audio decoder from a well-known German standards institute?). It simply is much easier for developers to work with with BSD license, as it does not attempt to be "viral" like copyleft code. Here is the code, don't sue the authors, end of story. Frankly it's somewhat impressive that GPL has done as well as it has, the necessity to only link with GPL-compatible code has become a pain point but the kernel project has enough clout to get people to license patches however the project wants (see: ZFS and the kernel devs trolling by relicensing files out from under them). GPL is actually an enormous pain from a licensing and corporate IP perspective and BSD avoids that.
- Number157 6y agoFor me, the draw of FreeBSD has always been that's it's one operating system. Linux, while small, is also fragmented. There is no "this is how to do X on Linux", as distributions are all different. So while there are strengths to having lots of distros, but there are also major downsides.
- loeg 6y agoI think FreeBSD will implement the io_uring API eventually. Maybe it will make its way into POSIX.