> the way computers actually work, with functions and parameters instead of icons and settings menus
Isn't "the way computers actually work" at a fundamental level about electrical engineering, or at least about machine instructions? If you're using Unix commands, hasn't a whole lot of work already been done to create the abstractions of pipes, file descriptors, files, filesystems, and so on? Is it clear that there is some sense in which these abstractions are faithful and true to the machine and technology, where other software abstractions are not?
We need different people to understand different layers, and as long as there are enough people paying attention to each layer, there's no problem.
I agree, which is why sometimes I think perhaps a toy assembly language might be a neat experiment from a pedagogical point of view.
As a child growing up, learning to function in society by speaking, reading, writing, and generally understanding English was a much harder task for me than learning to program in BASIC. BASIC is simple, predictable, logical and downright easy compared to English.
We take learning to read and write for granted, but its a messy, difficult, and often illogical affair. We have such high literacy rates because we start kids on it so young, and because its everywhere.
Its easy to imagine a version of our world in which children learn to interact with computers without GUIs, if CLIs were the norm. Children would learn them faster than adults.
Consider those children for whom learning a CLI was prerequisite to playing video games. All of those kids who I knew quickly memorized the requisite commands.
Ah yes, I still figuratively remember all the commands for loading Sinclair Spectrum and Commodore 64 games, and their "FastLoad" variants, typing in those PEEKs and POKEs from magazines for cheating/hacking, then the fiddling with AUTOEXEC.BAT and CONFIG.SYS while trying to juggle HIMEM and EMM386 and whatnot to be able to play DOS games..
It definitely piqued my interest in the workings of computers, spurred on by the generally more technically-inclined (not to mention humorous! oh how I miss CRASH and ZZAP!) magazines of the time, and it did get me into programming.
BUT, all that CLI voodoo was just a routine ritual to my other friends, in the way of what they really wanted (games.) They just had all the commands written down, and would rather ask someone than consult a manual when something needed to be done differently. They already had other interests. It didn't make all of them programmers.
So as with everything else, you can't really make a general statement that "X will make children do Y." People who are inclined towards doing something, will do that thing, on their own. I think what we (the adults) should focus on, is making things easier for them after the fact, after they've decided to get into programming.
Let's start with why the major operating systems of today require separate downloads and online research to get started with programming. macOS comes with that Grapher app, Windows comes with Paint, why can't they come with a nice coding app and some tutorials? So kids can just start poking away on their $500+ tablets and computers out of the box, like we used to on the C64, 20 years ago?
Do you want those children to hate CLIs because they are boring and they have to learn it just like all other boring stuff such learning how to read and write? If we offer children a way to enjoy what they are doing (i.e. make it fun to use/learn it), they will look forward to learning how to program. And making a task harder while it could be easier is not the answer (and children are not stupid, they would realize that a GUI would also be possible these days).
Furthermore, CLIs are hard to use in many environments. Would you want your waitress type "start paying; add product NAME [QUNANTIY]" instead of just touching the symbol a few times? There are many advantages with CLIs, especially when doing "traditional computing tasks" but in the real world, which is becoming much more digital, CLIs are not useable and a touchscreen with buttons is quicker. So why should the general public know how to use them – there are outside of our "edge cases" not really useful.
In this context, most of your post seems unrelated to mine.
> With no/slowed adoption of computers, it's not possible for programming to become more common than it is today.
"Not possible"? That's false on the face of it. You appear to be making unwarranted assumptions about what is possible in the relationship between (a) the amount of 'computing' in today's world and (b) the number of people who program.
The only non-cultural factor which really limits the possibility of coding is the availability of machines on which to program. I believe there were only around 20 million devs worldwide at the beginning of 2014. More PCs were shipped in the mid 80s in the US alone.
It is absolutely possible that a world in which the GUI was never invented could have more coders coding than a world in which the GUI had been invented. And the reverse is also true, of course.
Programming nowadays is easier than ever to get into. All you need is a computer, an internet connection, and the drive to learn.
If you bought a car in the early 20th century, you had to know how to work on it. Now, that's not that case.
Isn't that how a society works? The vast number of diverse human activities are only possible because of the echo-camber, of people who specialise in one area while remaining ignorant in almost all the others.
Also computing, and programming, is much much more than a unix prompt.
Some of us rather enjoy the way Xerox PARC envision the future of computing.
On that vision IDEs and REPLs like the Swift Playground are the way it should be, no need for a UNIX prompt.
I think it's more important for the younger generation to learn about other things, some of them I do not know.
Things like agriculture, law, music theory, etc. are much more important than programming.
> If computers had to be interacted with in ways that resembled programming - like a UNIX prompt
Maybe programming should start resembling GUIs more, instead of the GUI resembling programming more?
The only reason I got into programming was by messing around with HyperCard as a kid. HyperCard had an excellent learning curve. You could just use the pre-built stacks (stuff like an address book). Then you could start editing the controls (adding a field to the address book), then start using the prefab button generator or copying pre-coded buttons from sample stacks (say, to add a button to go to your own card in the address book). Then start hacking away at the scripts in the buttons (scripts that resembled english better than any language I've seen since). And this thing came with every Mac.
Today, you have to decide "I want to learn to program", look up resources, maybe do a tutorial. The only thing we have today that's close to "tricking" people into programming without them deciding to start programming is Excel spreadsheets. That's probably the #1 programming environment today.
In my opinion the use of a GUI vs CLI is more of a preference and doesn't explicitly assume the user is ignorant.
Yes. That's exactly how it would be, for whatever small fraction of current computer users were able and willing to adapt to that paradigm.
You're absolutely right about the separation between people who understand how computers work and people who only use them. Your second sentence in this comment is a brilliant example of the "echo-chamber wizard" school.
If computers had to be interacted with in ways that resembled programming - like a UNIX prompt - then people would be more used to the way computers actually work, with functions and parameters instead of icons and settings menus.
I really hope that raspberry PI gets more mainstream appeal as time goes on. I fear the separation between coders and users is creating parallel worlds of echo-chamber wizards and ignorant commoners.