I moved to PC-BSD and then TrueOS from Linux. (and kind of MacOS, I was using my Mac as my primary workstation for while). The reason I chose PC-BSD over vani

I moved to PC-BSD and then TrueOS from Linux. (and kind of MacOS, I was using my Mac as my primary workstation for while). The reason I chose PC-BSD over vanilla FreeBSD (or Ubuntu) was its integrated ZFS / beadm system, which creates ZFS snapshots at update time that are integrated with the boot loader. That means you can roll back if an upgrade fails, or breaks a crucial piece of software. There is less reason to do this now, as FreeBSD current now has decent beadm and zfs boot support baked in as of a few months ago. The things that I hate compared to MacOS and Linux: - No support for U2F in Chromium. In fact, if you have set up a security key, simply getting the U2F prompt will crash. See https://bugs.chromium.org/p/chromium/issues/detail?id=451248 https://bugs.chromium.org/p/chromium/issues/detail?id=451248 - Chromium version historically lags Chrome on supported platforms by weeks or months (though, as of today, I have chromium-56.0.2924.87_1, which is pretty recent). - No support for Google Hangouts (or other video conf. systems) - "Complex" Linux commercial binary software (like Chrome, slack desktop client, my kid's Kerbal Space Program) does not work with the Linux API support. To work around these things, I've actually installed a bhyve VM running ubuntu for Linux apps (and gone through the pain of routing pulse audio via a network socket so that sound works). With PCI-passthru, I can actually pass a USB controller into the Linux VM, so U2F and a video camera for conf. calls works. For KSP, Wine works reasonably well on the Windows binary. If I had it to do over again, I might just reverse things, and run Ubuntu for my desktop, and pass the disk controllers through to FreeBSD and run my FreeBSD stuff in a VM.