| > Long time OpenBSD fan. Used it as my daily driver for years before standardizing all computers at home to macOS. I still think about going back to openBSD one day, but it's no longer very practical as a daily driver. It's only practical for hobbyists. I used OpenBSD as a daily driver between 2001-2005. I fought, I suffered, I conquered, and I got tired of not being able to watch video on the web reliably and MacOS in those days was so clean and refreshing. I learned so much, though. > I want to use OpenBSD for the next project I'm building. I admire your open-mindedness. But ask yourself: 1. Do you want to have to upgrade fleets of servers every year with no exceptions for extended security support instead of 5 (or more if you're willing to pay) for LTS versions of Linux? 2. Who else will need to support it? 3. You will likely have worse performance if that matters. > 1. How do you deploy software? Honestly, not many people create their own services that run on OpenBSD. Those that do use old-school packaging and scripting. Tooling like ansible works. > 2. How do you manage fleets of servers? Ansible would be my go-to for classic fleets of servers. > How do you spin up/turn down servers from cloud providers? There are ports of cloud-init for OpenBSD. Creating images for third party OSes can be different levels of painful, depending on the cloud provider. |