> Also CLI tends to be more predictable
Generally I think that's true, but when learning Linux I managed to bork the system so badly using the command line so many times, that I just had to reinstall the whole OS.
Ultimately, if you don't have the ability to break things, you don't truly have the ability to experiment and discover.
I never recovered from losing a truecrypt password once.
Linux from scratch taught me that Linux is magic, and that if you deviate the slightest amount from the instructions, or try to customize anything, you are in for a world of pain.
The year was 1985. Against his hierarchy decision, my father bought one for work under cover of some big carbon paper order (that was used a lot at the time, so it really did go unnoticed) and hid it at home.
Bundled with the computer were two floppies with games, one with a rabbit in a maze and the other I can't remember. He booted them for me a few times. Then one day as he was gone at the office, I booted the thing on the DOS floppy, inserted the rabbit game floppy and started the game. I was caught red-handed when he came back. Boy was he angry (what if I screwed up and destroyed weeks of work?). It's actually the first time I can remember being scolded. Later when he cooled down and realized I could actually get it, he briefly showed me more things like LOGO and BASIC, which I enjoyed a lot. He did not know much on the programming front (he was more of a MultiPlan and WordPerfect user) so I was on my own on that front. I remember creating chains of GOTO to generate infinite loops on purpose, and genuinely trying to understand and build very crude purposeless but exploratory programs. Yet at that age and completely by yourself you really can't do much.
Then, less than a year later the computer gained its due recognition and went at the office, at about the same time we moved far away. I was not to touch a computer again for eight long years.
The biggest thing stopping people from using computers at that point in time seemed to be how expensive they were rather than that we had difficultly getting them to work.
I too could use the command line at a young age with the most basic things. I could even program a little back then. But I wasn't learning the fundamentals that way.
As far as I'm aware there isn't some universally recognized "right" way to teach people how to use computers. I remember 10 years ago everyone was certain that teaching kids to use MS Word was the most important thing in the world, now it seems to be avoiding creeps on facebook.
I'd be thrilled that they are actually learning something, especially something designed for "grown ups" rather than kids.
I am simply reacting and commententing to the overall theme of the comments and the OP's essay which is I read as him teaching his kids the fundamentals by playing around with non-GUI interfaces.
It's about time I start teaching my 3 year old daughter how to program a computer; hopefully she hasn't been too badly spoiled by the iPad.
There seems to be a popular misconception that a command line interface represents some kind of advanced brain surgery when in fact for many tasks it's simply easier.
I have done tech support jobs a few times in my life and it's a lot easier to guide someone in using a command line than it is a GUI "Click on Edit , click on Tools , Click the "advanced" tab , right click on the picture of a gear, now drag this thing into that place on the left" vs "type this in exactly how I dictate it".
Also CLI tends to be more predictable, I've seen so many people's computers where they've accidentally dragged interface elements all over the place and have no idea how to find anything.