My experience - more in the business world rather than end-user devices - is that it's easy to get swamped in the "cognitive load" of commercial software too.

Suppose you have a particular requirement: for a storage system, say. You search around various options, both commercial and open-source. The commercial offerings show you shiny marketing materials, but won't even show you the price until you engage with a salesperson and discuss your requirements. Then you'll get a "free trial". But the point is, this trial isn't "free" - you're investing your own time and energy in learning the vendor's product, how to install and manage it, how it might integrate with your own systems, what its limitations are (if the vendor is even open about such things). And then when you finally see the price, you may feel it's necessary to do the same for several other vendors' products.

In comparison, the open source software is much more up-front about its capabilities and configuration. The documentation is all there, you can read it, you can engage with other users and discuss your application and whether this software is suitable. If it isn't, they will know about the alternatives in this space and happily point to them.

Often there is a price tag with open source software too, where there is a commercial support offered. But that becomes a separate consideration: is this software doing a function which is so important that I'm prepared to pay someone else to fix it in emergency, or to add features that I require? Or am I happy to invest time learning the internals and fixing it myself - "doing my own yard work" as you call it? When a problem does occur, I already have a deeper understanding of the architecture and this helps with quicker problem resolution.

All this may have nothing to do with consumer software. The original Macintosh computer was conceived as a "toaster": you plug it in, and it works. The iOS app store model is very much the continuation of that approach.