News for hackers. Stuff that matters.
Re:Code rot and why I picked OpenBSD by yellowapple on Monday January 05, 2015 @10:18PM (#8842748)
I've been using OpenBSD for about a year now. It's still not quite my daily driver (it's running on one of my three main workstations - a PowerBook G4 - but not on my desktop or my other laptop, both of which are still running GNU/Linux - Slackware and openSUSE, specifically and respectively), but it's certainly the OS of choice for my servers.

OpenBSD appealed to me as a Linux user for the same reasons why Linux appealed to me as a Windows user. I was tired of bugginess, and just wanted things to work. Unfortunately, I still have the same obstacles migrating to it from Linux as I had migrating to Linux from Windows - namely, hardware support and gaming - that keep it from being my dream OS; however, it's still the OS I like to use when I need to get real work done (just as GNU/Linux was the OS I liked to use when I needed to get work done, back when I was still a Linux/Windows dual-booter so many years ago).

Even with those shortcomings, my PowerBook G4 is currently my favorite machine. There are some kinks, to be sure (power management is non-op, so I can't put the laptop to sleep), but with OpenBSD and WindowMaker, it's pretty rock-solid despite its age.

The nice thing about OpenBSD is that the devs aren't afraid of breaking backwards-compatibility if needed. They've already solved the 2038 problem as of 5.5, for example; with Linux's policies on backwards-compatibility, that'll be a nightmare to fix on 32-bit Linux systems (and even other BSDs, if I understand correctly). To me, that's awesome; I'll take a minor flag day to clean-reinstall my servers now over a major flag day to hack together some kind of band-aid "fix" later any day, and it's nice to know that, should I setup a server right now, it won't spontaneously vomit all over itself in 20 years or so due to it suddenly thinking it's 1970 again.

There are no comments on this comment yet.