OpenBSD combines two seldom used techniques. First, not having millions of lines of code written by random untrusted people. This allows them to use the second technique, which is to actually read their code.

Well, that is not good enough. How can you proof that already read (audited) code wasn't tampered afterwards by a hacker? If you don't use cryptographic hashes you can't.

And many women go through 3 pads a day during their peak. Which is much more convenient than having to change your underwear, and have somewhere to put them to carry them around with you until you get home.

Those "many women" may have menorrhagia and should consult with their doctor for treatment, yet very few realize this and just think they are "heavy flow" people, which puts them at risk for disease and other medical problems. I should think, though, that it's much more convenient to carry around one pad than three, and for the rest of people is probably a relief to not need one at all.

Xen, Minix 3, QNX, several l4 implementations, etc. OKL4 alone has been shipped on over 1.5 billion devices. QNX was huge. Xen is running everything at AWS, the largest webhosting company in existence (nevermind everywhere else it is used).

QNX is huge. If you took QNX out of the world it would stop to function just about immediately. So much stuff runs on it that you typically wouldn't even guess. In that sense it is just like other soft real time/hard real time OS's one of the unsung success stories of IT simply because it works so well it tends to disappear.

Most things that use QNX or other OS's like that inside simply work rather than that they require constant upgrades and bug fixes. Reliability by design is so much better than reliability by trial and error, and the OS is a huge factor in that. It's a world where bugs are felt as 'egg on your face' rather than a 'wontfix'.