@gme @stefano I don’t think that’s entirely fair — I kind of see your point, but the difference is that you can in principle find someone else who can manage a FreeBSD server or even an OpenBSD one.

[benjamineskola@hachyderm.io]

@gme @stefano I don’t think that’s entirely fair — I kind of see your point, but the difference is that you can in principle find someone else who can manage a FreeBSD server or even an OpenBSD one. The pool of potential sysadmins might not be huge, but it’s there. It’s not at all the same kind of vendor lock-in as Google or Microsoft.

(You’re right, though, that there is a value in choosing a more widely-adopted system. But it’s not unlimited value otherwise we’d always just have to choose Google or Microsoft despite the lock-in; there’s also value in it being open and documented.)

[stefano@mastodon.bsd.cafe]

@benjamineskola @gme no lock-in involved. I proposed several solutions and they decided they want OpenBSD as they're already using it for some services (mainly ssh and VPN endpoints) and they appreciate it. Their internal IT staff is able to manage it on their own, at least for basic stuff.
Mailcow is nice - I'm using and installing it when needed, but it's another "product". Having different components involved means being able to replace them individually.
But yes, I can understand your point of view and you're not wrong.