> ...also having used all BSDs for a week each. On bare metal, or virtualized? > ...lack of GPU acceleration Depends, for some older chipsets it was there, f

> ...also having used all BSDs for a week each. On bare metal, or virtualized? > ...lack of GPU acceleration Depends, for some older chipsets it was there, for me, then. Though I have to concur, that is annoying, when your's is much too new, and thus badly supported, if at all. > ...shady Bluetooth and Wi-Fi support I'm a caveman and really don't care about that. Not even under Linux :-) > ...and overall slowness Yes. That was unimpressive. But it went away after https://www.netbsd.org/docs/guide/en/chap-kernel.html https://www.netbsd.org/docs/guide/en/chap-kernel.html and even more so after https://www.netbsd.org/docs/guide/en/chap-updating.html https://www.netbsd.org/docs/guide/en/chap-updating.html with https://pkgsrc.se/devel/cpuflags https://pkgsrc.se/devel/cpuflags ( Could probably be done from elsewhere with https://www.netbsd.org/docs/guide/en/chap-build.html https://www.netbsd.org/docs/guide/en/chap-build.html also, because cross-compiling is built in! ) Lastly applying some https://www.netbsd.org/docs/guide/en/chap-tuning.html#tuning-system-sysctl https://www.netbsd.org/docs/guide/en/chap-tuning.html#tuning... That sounds all really complicated and time consuming, but at the times it wasn't. Because the base is smaller, the compilers were faster. Expecting it to perform out of the box without adapting it to the environment will lead to frustration. It really can fly.