http://boingboing.net/2012/08/23/civilwar.html
http://boingboing.net/2012/01/10/lockdown.html
I mean, how do you even convince someone that learning to program is a good idea if it takes jumping through many serious hoops just to set up? The majority of interaction with computers is with locked-down mobile devices. Contrast this with home computers in the 80s that were practically begging to be programmed as they came with little other than a built-in interpreter, or the early days of the PC where user magazines had source code - in assembly language - that people could enter in DEBUG and create small but useful programs.
The walled gardens of app stores have also grown to the point where simply sharing an executable with someone has become an almost taboo act, with some central authority telling the users who to trust.
It's in the interests of the software industry to keep the majority of users computer-illiterate, so they can be profited from. On the other hand, basic literacy is valued by the industry, because it makes it easier to persuade users who know how to read and write (adverts wouldn't work if people couldn't read them...)
Setting up a development environment is an absolute pain in the ass, for a professional developer. But when I was in middle school on my pops pre G3 apple computer (or maybe it was the G3 at that point I'm not sure) I pretty easily figured out how to use a text editor and a preinstalled language to solve project euler problems. Boy those were fun.
I'd imagine access to the computer is a big issue, and only god knows where I found projecteuler for the first time but those sparks are really whats needed. If it ends up getting taught in some stale way as proofs in highschool were taught with lots of rote memorization and none of the art it'll probably end up producing a similar amount of interest.
Also, I presume, as people get older they're less likely in many cases to spend the time to learn a skill which doesn't offer anywhere near the tangible benefit of speaking and writing. Speaking and writing are practiced near constantly just because they're generally the best tools (along with drawing, gesturing, touch) for a job (communication) which must be performed everyday. I can't imagine the future where programming ever hits that level and see it more like the internals of a car with its standard bellcurve distribution of understanding across society.
In fact, I'd say that it's more accessible because it's on a locked down, easy to use device.
...although perhaps it would be a great time to talk about how things used to be different, when such questions come up.
But now you are moving the goalposts.
It is irrelevant whether programs are "first-class citizens." It doesn't stop one from enjoying and experiencing programming, and it certainly doesn't prevent someone from making just as complex and interesting programs regardless of the environment in which they are executed.
The point I am arguing from your original post is the following:
> Unfortunately I don't know if it ever will reach the same level of importance as literacy, because the industry seems to be trying very hard to discourage regular users from ever becoming programmers or even "advanced users"; see the War on General Purpose Computing:
I very much disagree that anyone is trying to discourage regular users from becoming programmers. Whether you are in a sandboxed or locked down environment is an irrelevant implementation detail. Virtual machines can be explored on such systems, even if the real ones can't.
(And, as an aside, Codea for iPad can export a user's project into a native app that can be developed further or uploaded to the App Store. So even environments like the iPad can, and have, produced "first-class citizen" applications. In fact, we published the first game coded entirely on iPad in 2010. It has had millions of downloads.)
This is entirely because of malicious people ruining it for everyone though, not necessarily that the app stores just have the monopoly
Programming seems more similar to car mechanics to me. When the car was first introduced, everybody who owned one knew exactly how it worked and how to fix it. Partly because they were simpler and partly because the early adopter were just more interested. Over time, as the complexity and ubiquity of the car has grown, the general population knows how to operate a car but not how to fix it (save for some basic things here and there).
Similarly with computers. The increasingly abstract operating systems, UIs, and even languages have created stratifications of knowledge across the whole stack (IT, software devs, compiler writers, CEs, etc) . Most people using a computer do not know how it works anymore, just like with cars.
I think it's great that schools have to offer computer science because it's a great subject that young people can really take off with since writing software costs so little compared to other hobbies. But it would be silly to force people to learn to code. As much as computers are becoming the most integral things in our lives, it's just not a skill that everybody needs to have.
It's been about a couple decades since I wrote my first for-loops and if-statements in Qbasic...but even though computers have grown exponentially, not just in pure power, but in influence and capability -- I use the exact same logic and thinking, every day, as an application programmer -- and very close to the same syntax.
Loops and conditionals (and functions, and so forth) are so fundamental to programming that it seems like anyone could learn them -- and use them to some practical effect -- in a few hours of following a few tutorials. But I haven't seen it in the beginners I've taught...It's a profound thing to communicate my exact intent to a thing that only knows, at its core, 1s and 0s...but it's not just the ability to write code, any more than writing is just the ability to make dark marks on a piece of paper. It's the ability to take thoughts and intents inside of me and communicate it to something fundamentally different from me, and yet be understood...in that sense, it's not so much different from traditional writing.
I think that you are underestimating this. It took so long for reading and writing to become common skills because there had to be a social shift for more people to stop farming and get an education. Shift from one type of education to another is much simpler.
These days, you'd have a hard time finding parents who would be opposed to their kid learning programming instead of just about anything else.
More and more of the job of programming will be handed over to machines. Meaning that the work will become easier and easier and the skills required will change as time passes.
The other issue is the amount of time required to do anything useful with the skill. One you learn how to read you can read books quickly.
If you learn how to code, it'll still take you 6 hours at least to produce anything that would be even moderately useful. If you try to use computers to optimize everything, you'll waste more time on the "optimization."
What? No way. I crank out extremely useful shell scripts in less than 5 minutes all the time. You don't have to use an IDE, compiler and some heavyweight framework just to be a programmer. Cobbling together a quick shell or Python script can let you do TONS of tasks that would be extraordinarily tedious, if not impossible, for a non-programmer.
I think public schools (and schools in general as an institution) face the same problem universities are facing: the obsolescence on such a mechanism to effectively and efficiently disseminate knowledge as more and more resources are allocated for signaling of such rather than acquiring/pursuit of it.
[0] http://avc.com/
I do agree schooling is starting to disintegrate.
20 years ago, learning programming wasn't as important because the technology just wasn't there to make it a good return on investment. But the value of reading and writing was also relatively minimal when it cost a fortune just to make a single copy of a book. If programming is how we turn human thought into machine-understandable commands and subroutines, and more and more of our work is delegated to machines...it's hard to imagine the long-term argument against learning programming.