I see so many more cryptic comments about their mailing list than actual description.
Anyone have a good resource to catch up?
In the meantime, I recommend my perspective to anyone who asks (nobody asks): separate the OS from the dev mailing list.
Anyone have a good resource to catch up?
In the meantime, I recommend my perspective to anyone who asks (nobody asks): separate the OS from the dev mailing list.
It's just not a very friendly list, or at least it wasn't in days of yore when OpenBSD was relevant.
You have to realize that a lot of BSD enthusiasts are people who have let "being a *BSD user" subsume their whole identity and there's a lot of "Linux is for noobs"-style elitism.
You do realize that a very _very_ large number of us here use OpenBSD code literally all day every day?
Who do you think wrote OpenSSH? Or do you remember Heartbleed, when everyone switched or thought about switching to LibreSSL?
Just because most of us don't run OpenBSD-the-OS very often doesn't mean we don't all frequently use it's code.
OpenBSD fans like to make a lot of hay about its vaunted security posture but in real-world use cases I have no doubt that properly configured and up to date FreeBSD, Linux or even Windows Server is just as secure as OpenBSD.
There are just vanishingly few reasons to use OpenBSD today.
The documentation does tend to be pretty good, but... honestly? I just don't find that to be a compelling reason to choose an operating system.
I do feel quality documentation makes a huge difference. Navigating the broken-links craziness of FreeBSD documentation was just such a frustrating experience. And even on a "first-class-supported" system at the time, they omitted a KEY (IMO) piece of information that resulted in me being unable to even run the OS until I did hours of research on OpenFirmware and realized the missing piece in the process. I could see from online discussions that most people had completely given up on FreeBSD at the same point I reached.
Ah well, for me, I don't notice any "warts" of any sort with OpenBSD, so whatever problems other people have just don't affect me or aren't relevant to my use case(s). Such is the case for any OS, I think ppl should use what works for them. No use discounting an OS completely just because it doesn't work for your purposes :)
wheeze Windows Server??!! This beggars belief.
I'll give you a hint. It's not BSD.
https://www.wearethemighty.com/mighty-history/worst-cyber-at...
Whereas openbsd people kept that attitude, the gnu+linux people went above and beyond to help newbies. Help not only in fixing their stuff, but also in growing and learning.
And I don’t buy the “secure by default” marketing stunt. At best you’d have to put that in the context of an OS that does a limited number of things, and does them poorly (questionable ux, poor performances). Gnu+linux is secure enough, particularly so if you compare that with the incredible amount of things it can do.
As someone using Debian, Ubuntu, OpenBSD, and other OSs regularly, what I'm experiencing is perhaps less "elitism" on the BSD side, and more of: "hey, we're also here, it would be nice if you could consider us sometimes". The BSDs traditionally have different ways of doing some things, which are equally as valid, but e.g. OpenSSH considers the needs of Linux users, and provides sandboxing through seccomp[1] (which NB is quite an achievement to get right, contrast with pledge[2]).
[1]: https://github.com/openssh/openssh-portable/blob/master/sand... [2]: https://github.com/openssh/openssh-portable/blob/master/sand...
Meanwhile e.g. on the systemd or GNOME side of things, projects tend to act not only as if Linux was the only platform in existence, but almost as if any alternative or adjacent technologies had no right to co-exist either: e.g. when GNOME told SDL2 developers to link against GTK to draw native window borders under Wayland[3]; or as systemd continues to swallow every traditionally discrete UNIX service, such as cron or syslog, and tries to shove DBus into the kernel. This is a stance that I'd expect from Apple (who are shipping an opinionated but highly polished and desirable product), not an open source community, where value emerges from collaboration.
[3]: https://gitlab.gnome.org/GNOME/mutter/-/issues/217
Of course there are plenty acts of both generosity and jackassery in all of these communities, however the picture you're trying to paint is a bit unfair.
Poettering hates everything that he hasn't touched. This is well-known and why anyone that cares about Linux and what it stands for should not use any OS that is infected by his projects.
Gnome 3 isn't worth the price of Systemd.