A car needs 4 wheels and tires. If it lacks that basic stuff, it doesn't matter if it's a Rolls Royce or a Ferrari, it's not rolling! ...
If I don't like the brand of the tires the car came with, I can get them swapped out later.
In the old days, before about 1920 or 1925, many cars came without bodywork: No seats, no sheet metal, no doors, no roof. You ordered the frame and running gear (engine, transmission) from the car manufacturer, and then had it completed by a coach builder to make it drivable and useful.
For some vehicles, this is still true. At home, we have both an International 4300 (today the model is called the International MV), and a Ford F550. When you buy them, they have motor, transmission, frame, wheels, and the cab (the part the driver and passenger sit in). The whole back is empty and wide open. You then have it shipped to a specialty upfitter and install whatever you want. We happen to have a Terex Commander 4045 on one of them, and a Rugby DumpBody on the other.
I happen to like the same paradigm for my server OS: I install FreeBSD, and I expect it to be completely useless, and have no functionality. I then add the various functions I need: I set up user accounts, large file systems, NFS server. I download packages for DNS, DHCP and NTP server, and populate their config files. I install and configure Apache, and place all the web content in the correct directories. I fetch my personal server software from the source control repository, make the required hardware connection (today that's down to a few USB and serial wires), and start using it. FreeBSD is excellent at delivering this experience, without getting into my way, and without causing me to tear my hair out over bizarre configuration choices, or "the OS knows better". FreeBSD (and the other two BSDs) implement POLA better than any other server OS.
But note that this is for a SERVER machine, which has no GUI (the fact that it even has a VGA port and a keyboard attached is really just for emergency maintenance, when all the network fails). For my desktop (laptop) machine, I prefer a totally different paradigm: I go to a store, give them my credit card, and they give me a cardboard box. At home I open the box, plug in power, and I type in about 3-4 pieces of information: My account on a big cloud computing organization, my password there, the desired username and password on the new laptop. And I select the correct SSID for the WiFi and enter its password. After about 30 second, I expect the GUI to come up, and be configured exactly the way I like it, the way it is on all my other laptops. The screen background will be correct, the icons are all in the right places, and the application menus are populated the way I like them, not some OS-specific default. After about 30 minutes, I expect all my e-mail to be downloaded and cached, all my web resources to be ready and cached, and all the files of which I desire to have local copies to be present (it takes 30 minutes because our network at home is slow), without me having done very much to make it happen. There happens to be a product out there which can deliver this user experience to me (and a similar user experience on cell phones), and it is not FreeBSD.