Everything I learned about OpenBSD in the 00s is just as relevant today. The muscle memory all still works. Whereas on Linux I've gone from `ipchains` to `iptables` to `nftables`, etc. OpenBSD still uses the same pf.conf and it works great. It also has the most beautiful rc.d system I've ever seen, whereas I can never fscking remember what the flags are for `systemctl`.
The only downside to OpenBSD is that it's not so compatible with Nvidia cards, which is a bummer if you do anything with CUDA.
I think 'skill expiry date' is an underappreciated design requirement, and one that only gets more important for you with each year.
If we can justifiably look askance at Chromebooks with 3-year lifespans, we can and should give the same sideeye to platforms that make us (or at least, our marketable skills) disposable after 3-5 years.
Everything I learned about OpenBSD in the 00s is just as relevant today. The muscle memory all still works. Whereas on Linux I've gone from `ipchains` to `iptables` to `nftables`, etc. OpenBSD still uses the same pf.conf and it works great. It also has the most beautiful rc.d system I've ever seen, whereas I can never fscking remember what the flags are for `systemctl`.
The only downside to OpenBSD is that it's not so compatible with Nvidia cards, which is a bummer if you do anything with CUDA.
I think 'skill expiry date' is an underappreciated design requirement, and one that only gets more important for you with each year.
If we can justifiably look askance at Chromebooks with 3-year lifespans, we can and should give the same sideeye to platforms that make us (or at least, our marketable skills) disposable after 3-5 years.