As a matter of fact, I don't think this has anything to do with linux itself, just with the large distributions. If you use alpine, slackware or void you get a similar streamlined experience.
openbsd will definitely feel from 10000 feet more "bloated" because its simply not as performant as linux. that's not a bad thing, it purposely does things the "right" way for security purposes and doesn't take any shortcuts.
alpine is a lot smaller than openbsd but it really was created for an entirely different purpose. i always take alpine as "a muscl distro that makes a good docker container, oh and it runs on bare metal too, i guess". i've never seen alpine on metal in prod and i've been around the block a whole bunch. ive seen it in a metric ton of docker containers though.
a chatty dmesg also isn't really bloat as well. although dmesg is a bit of a mess (and only recently default restricted to privileged accounts at least on arch).
OpenBSD might not scale well to a large number of cores, and the program running on a 8-bit microcontroller (with 512 bytes of ram) on my breadboard isn't fast, but neither are particularly obese.
I don't think the purpose between Alpine and OpenBSD are that far apart. Alpine aims to be a simple, small, and secure general purpose OS. OpenBSD is very similar, even if Theo has been pushing the "research OS" angle. There's obviously a big difference in how much software include in the base install.
It kinda is. Totally unrelated, but there is nothing quite like seeing hundreds of [nfsd] tasks hard-blocking in D on each server in a cluster. Time to reboot... well... everything.
The list is pretty short on my alpine install if you exclude kernel threads:
I don't think kernel threads are a good measure of bloat. And a base install of Alpine is smaller than OpenBSD.But that's a fair point about presentation. OpenBSD seems to be more 'quiet' by default, and tends to only show relevant information. dmesg on OpenBSD seems much cleaner compared to the mess that Linux outputs.