I don't care much about advanced security or networking features but I use OpenBSD because of its simplicity and the quality of its documentation.
Other than a few esoteric situations like that one though, I agree: OpenBSD's documentation is pretty darn good.
I like them primarily because they're sitting in a corner quietly doing their own thing, and their own thing happens to be a very stable & very reliable network service operating system with an emphasis on security and performance. It's a refreshing change from the ADHD present in the development communities of other operating systems.
OpenBSD clean and simple design makes it a breeze to maintain. It's documentation always tells you the whole truth and for most tasks, its so intuitive that you almost always already know where to do your stuff.
Funny, I care very much about security and both OpenBSD and FreeBSD are primarily on my radar for that reason. Nice to know I get the simplicity too.
In my case I use it on a personal computer and as long as I've got X.org and network connectivity I'm happy. By default OpenBSD doesn't have much software installed. In term of user software, you get ksh, vi (not Vim), optionally X.org with FVWM and I guess that's pretty much it. Then you just add what you need. Oh you also get Tmux, which originates from the OpenBSD project.
Wasn't sure until recently if I could use OpenJDK with the framework I'm using, but it seems to be compatible, so am starting to look at Free/OpenBSD + OpenJDK for it.
Tmux, ssh, and vim are good enough for the server side IDE, so as long as vim is in the repo's, should be gtg. :)
(Not snarky; an honest question to verify my older "machine park" for an install to play around, which I've wanted to do for a while.)
Unless you have some really weird hardware, I'd be surprised if OpenBSD didn't support it. The best way to check is to boot an iso and look at the output of dmesg, however.