I would say it's OpenBSD.
My first BSD is FreeBSD. After that I played a bit with virtualization but unfortunately my CPU too old and not supports VMX. NetBSD is the only BSD could run on Virtualbox with this
trick. So I love NetBSD. Where other OSes refused to work, only NetBSD runs. It reminds me of my loyalty black dogs. But they both gone. I'm also given up on NetBSD. Now I've an upgraded system with full VMX and VT-d capable. I could play with NetBSD further. So bad I realize, the system is blazing fast with 4 cores and 4G ram, even boot up faster FreeBSD with the same configuration, but software is severely lacked. I means binary packages I could install with pkgin. Sometimes
pkgsrc.se list the port as available but it corresponding binary package is not found (not yet built? I don't think so. I think it can't be built, so it's unavailable, it's also means the port is indeed broken). You know, packages for firefox, codeblocks, codelite, chromium,... and so many commonly used software are unavailable. Left me with only seamonkey that works and reliable, but the porter forgot to create a desktop entry for it, so I've to start it from the terminal. I tried my best to bring the system to a working state, and I partially succeed with a MATE desktop started via .xinitrc (there's only slim-themes but no slim package, ironically!), seamonkey, geany, libreoffice, ibus. I also not have much success with pkgsrc other than building basic port like bash, joe, nano,... whenever you started to build gui based apps it will be full of problems. Made me wonder, it's the same pkgsrc, how could they deliver binary packages to me, when I can't built the ports myself at all? And I switched to use NetBSD as a server, I not yet want to give up on it. But the lacked of software stopped me again. I want to setup a svn server with NetBSD VM, and I can't found mod_dav_svn anywhere. I changed to make it a NFS server, despite it's only has NFSv3 but if I could find a useage for it it's better than nothing. Then I also realized I've to use brigde interface and to my surprise, how fast it is with NAT how slow and unreliable it is with bridge. So I given up on it completely.
To my sincere, I advised NetBSD to follow the way of SmartOS, become a hypervisor OS and only that. It has many potential: going to have up to date ZFS ported from FreeBSD and the new NVMM. When you can't compete with other on the server side (web servers, mail, file servers,...) and don't have the resource to catch up Linux on the desktop side this is the safest way for you. I heard people said NetBSD also has potential on the embedded side but I don't know anything about embedded so I don't mention it.
Someday I would try NetBSD again and check if I could use it as a hypervisor OS or not.
Back to the topic, I choose OpenBSD because I think it's a better NetBSD than our current NetBSD. DragonFly also has many impressed features but the last time I tried it on Virtualbox (5.6.1?), the HAMMER2 FS just unreliable, after I installed MATE and set everything up in rc.conf I restarted and HAMMER started to fail, if I'm not wrong something about malloc error. But I don't blame the developers, though. They've done incredible job even though they're such a small group.
) I doubled sales at my CompUSA store in one year. For the rare techie customer I could hit a key and switch into a KDE interface and show "unix" but for most customers all I had to do was slowly pull the mouse pointer down to the dock, watch the beautiful icons expand as I hovered over them, click one of the icons and watch it do its cute little jumping up and down while the window opened. Sold!
