I am making this thread, because I found some quite old threads of a similar kind, but nothing that's organized or that discusses the issue at any given time. Having the right keywords also makes searching for this info hopefully easier.
The question for this thread is:
What evidence-supported strengths does FreeBSD have over a major Linux like Debian 12?
I just want to understand the strongest areas where FreeBSD shines over Linux or is at least equivalent.
---
The main motivation for this thread came from this speculation around this other thread:
How would one ever get around the issue of non-matching syscall interfaces?
I don't know how one can even expect that one could model another (operating) system 1:1 on another one. They would have to be the same system in that case?
Also, possibly, such effort would be better to be done towards GNU Hurd/Mach:
which also bakes in the drivers available for Linux, or writing the drivers for FreeBSD.
Also, in this context one would desire "portable drivers".
BTW,
I'd rather port the BSD userspace...
That is, in order to understand what's a smart way to "connect" the OSes, then one needs to know where their strengths lie, so for most part one can combine the strengths of each OS.
---
I suggest this thread can be used as a standard thread for questioning the status quo at any time (week, month, year, ...) so that new threads about GNU/Linux vs FreeBSD do not need to be created.
I somehow foresaw that kind of thread coming up again.
Regarding linux, I liked it before systemD, pulseaudio, and pipewire became a thing.
But if you ask me now, whether I would move back, or even considering using linux ever again, I would say no, and there are reasons for that.
1) SystemD:
I would recommend reading
that thread among others, or at least part of it, since it describes the attitude of systemD developers and their concern for the userbase.
According to
CVEs systemD is very much vulnerable, and has some severe security risks.
My personal experience with systemD is that it deleted my /home partition, and encryption headers beyond any reasoning, I could understand.
2) Pulseaudio:
I liked Alsa, and it worked almost out of the box for me, but I needed per app audio control later on so, I switched to pulseaudio.
I never got it to run without crackling, almost spending 2 weeks on it.
Latency problems were also severe for me, but at least I could fix them.
The overhead caused by running an audio server on top of an audio server was also not excusable for me.
3) Pipewire:
A low level framework for audio, I believe.
Spending about 3 weeks on it, I really liked the customizability, and the easy setup of parametric equalization.
However, same problem, the audio crackled.
Again extending ALSA would probably be better, instead of throwing another audio server alternative which depends on either an audio server like ALSA, or jack, or pulse, which also depends on ALSA.
4) Linus strange behaviour regarding the linux ecosystem:
-> Signing a CoC created by Coraline Ada Ehmke with its quirks.
-> Throwing out kernel driver maintainer only because they have
a certain ethnicity.
Who is going to maintain these drivers now after the person in response are no more?
An operating system should serve the user, and not work against the user.