1,186 karma · joined September 4, 2019
I personally worry it's not interoperable enough.
Locking down an Openbsd system is quite easy for example as it tries to have sane defaults. I find myself more in the dark with Linux.
Installing zfs on Linux is possible, but again can be a lot of work and it doesn't cleanly integrate with containers the same way zfs integrates with jails on Freebsd.
What they all have in common is that they have great documentation, and they're all very unix-y and all have some virtualization support for linux.
Some things FreeBSD offer are good performance, IME the largest package repository, zfs integration, capsicum and jails. The experience IMO is a bit like Arch, except you'll rely less on a wiki and more on their official documentation.
OpenBSD and NetBSD offer a more "complete" experience like you'd expect from a desktop OS, while at the same time being quite minimal and simple.
OpenBSD focuses a lot on security, and is probably more likely to work with your hardware with fast wifi. It doesn't offer the same virtualization nor security the same type of security as Linux, but instead encourages you to pledge and unveil your applications, which means you lock down each application by saying what it can and can't do. It notoriously removes features from the kernel that are unmaintained and also doesn't include things it considers insecure like bluetooth. It's probably the OS that gives you the most "works out-of-the-box" experience.
NetBSD gives you a full desktop experience as well, but also has some unique security features like kauth, veriexec, extra-hardened chroot and security.curtain. It also offers some cool features like rumpkernels, smolbsd, and is probably the easiest to hack and compile yourself (even cross-compiling is very simple). It has a package manager, pkgsrc, that runs on many other OSes and it's also quite easy to port to new platforms. It's a fun OS to tinker with.
A big part of interacting with APIs (which I imagine Stategraph does) is just dealing with records, and working with records in Haskell is really annoying unless you bring in lenses which bring a lot of complexity.
They are. So. Slow. Each and every one of them. Its awful
But otherwise I don't particularly agree with OPs pain points. I personally find OCaml's syntax to be great. Very easy to write and read once you're used to it. And I previously thought that it's very important to annotate all types, as it would help with my thinking, but these days I find I'm more productive when I write out the code without types, maybe add a type here and there. I only annotate if OCaml's deduced type is too complex or generic.
Efficiencies lead to less resources being used if your demand is constant, but if demand is elastic, it often leads to the total resource consumption increasing.
See also: Jevons Paradox (https://en.wikipedia.org/wiki/Jevons_paradox).
https://lobste.rs/s/pmfuza/bro_ban_me_at_ip_level_if_you_don...
https://github.com/kusumi/openbsd_hammer2
Somehow it was just never taken over the finish line though. I don't know why.
For those who want to check it out now: there is documentation but for the nitrosshd documentation. The sshd service works the same, minus nitro of course.
sudo chattr -i $HOME/.shrc
sudo chattr -i $HOME/.profile
to make them immutable. I also added:
alias unlock-shrc="sudo chattr -i $HOME/.shrc"
alias lock-shrc="sudo chattr +i $HOME/.shrc"
To my profile to make it a bit easier to lock/unlock.
[1] https://limited.systems/articles/climate-cost-of-ai-revoluti...
People barely know what a file-system is these days.