> Netbsd can run on any device possible and I really appreciate it.
That's more of a meme than reality and I wish people would actually look into it before mindlessly repeating the trope. I did, when I wanted to run a new OS on a niche device, and the reality is very different. Nowadays Linux works on a lot more hardware than NetBSD does. Yes, NetBSD nominally supports a few more architectures than Linux (very few, especially that μClinux is now upstreamed), but the driver situation for the rest of the system means that it can't run on most devices from those architecture anyway.
This and 'runs' is a very relative term. What exactly works, what doesn't? What do you need? How power efficient or buggy is it? How is the performance? I remember running Linux on an SGI Indy. Not everything worked, as not every Indy was equal (I had six) but also compared to IRIX (especially 5.x series) the performance was dog slow. The Indy had some good hardware (like the soundcard or Indycam) but that wouldn't work (well) on Linux. My Octane 2 didn't have 3D accelerated graphics on Linux. The state of every port isn't equal. Same on OpenBSD. Furthermore, if you run Linux your distribution of choice may not be available or work well.
That's more of a meme than reality and I wish people would actually look into it before mindlessly repeating the trope. I did, when I wanted to run a new OS on a niche device, and the reality is very different. Nowadays Linux works on a lot more hardware than NetBSD does. Yes, NetBSD nominally supports a few more architectures than Linux (very few, especially that μClinux is now upstreamed), but the driver situation for the rest of the system means that it can't run on most devices from those architecture anyway.