Do you only do those things you know how to do then?
Ah. So, not a 'pioneer' at any level?
When I was at secondary school in woodwork classes we were given the choice of making book-ends or a bathroom cabinet. Because I didn't read (for fun) I didn't need any book-ends and because I didn't own a bathroom I didn't want a bathroom cabinet either, what I didn't have but did want was a boat. My teacher asked him if I had ever built a boat before and I said I had not. Then he asked how I knew I was able to built one and I wouldn't know till I tried. So, I built the boat (and still have it) because I knew I had the basic skills I needed to do something I had never done before. Same with building the kitcar after doing all the bits individually on different vehicles over the years.
So I did something I had never done before with little in the way of guidance from anyone and by just following some basic plans and general building guideline (like which glue was best and how to bend timber without a steambox etc).
My point was that much of what I had to do was for me and at that time, 'trial and error' as such, because that principal doesn't stipulate the ratio of error to trial. If you read Johns TV Box Wiki you will see he made mistakes because he hadn't made that actual thing before, even though he had done most of the processes before. That was the 'error' in 'trial and error'.
Not 'again', 'exactly'. So, you have to look at the *typical* userbase for most desktop OS's and then consider just how much involvement and 'learning' you might consider to be a minimum requirement. My point was that it *is* (unquestionably) easier to lean something that you can explore than something that heads more traditional study.
But that is just the OS itself, there is nothing stopping people writing other modules like drivers and applications.
But why should it be so different re user-administration, especially in 2017? The answer is 'it shouldn't' and if all the people working on Linux stuff, doing their own thing, forking distros every which way, spent time refining the admin GUI to be more, 'GUI' then maybe my list could include Linux?
And it is my prediction that one day it might, making any counter argument pretty mute?
Something that can be intuitively explored is easier to lean than something that can't.
And most wouldn't want to (including me), ever.
I am talking about just administering the OS from an admin-users POV. So, that's not developer or end user just using what they are given with it all working (as well as it can be).
So I am talking people like me who might like to be able to fix more of the many things that often don't work on Linux with hardware OOTB that work with Windows OOTB because in most cases there is official support for Windows from the hardware manufacturers and software writers.
Linux is currently still that harsh square peg in the generally friendly round hole that is Windows (OSX / Android) world.
Slowly though the square is being rounded (as even I have seen over a good few years now from not being able to install Linux and even get it working, installing it and having some things working (wired Ethernet if not Wireless, some video display rather than none) to it generally working as long as you are a bit lucky).
My point is that *my* low level skills re Linux admin haven't really improved yet my ability to get to a fully working (basic) machine has.
It seems that many of the Linux zealots can't or don't want to acknowledge the weakness at this level and simply think that making people have to do something (learn how to use the OS at a lower level) is a realistic / practical solution to the issue, rather than simply bringing Linux up to speed in 2017. ;-(
Cheers, T i m