The point is that children start to dislike maths once they go to school. And they do - all kids in my class either already knew basic maths before going to school or were completely bored by it.
The same will happen with programming once it will be "taught" in schools as well.
Think of it this way - if you want people equally competent as you to teach your child in school, you have to pay them 1/n of your salary, where n is the number of students in class. If you pay them less, they will find a better paid job elsewhere like you did. And you don't want n to be large since it's hard to pay attention to more that a dozen of kids at a time.
Hence, school must either consume 5% to 10% of your salary per child, or be ran by people less competent than you. It seems that usually the latter is the case.
You can get a bigger n, not by increasing class sizes alone, but also by letting teachers teach for longer per day than children learn. I.e. use you math per hour taught, not for salary.
What this means in practice is, use teachers for higher value added work, but let computers (or somebody less qualified) oversee other parts of the learning process.
What seems to work fairly well (I remember a study about it), is to let students read material at home, but solve problems in class. That's the opposite of the traditional getting lectured-at in class / exercises as homework approach.
Khan academy is another vector for leveraging teachers. It does not replace a good teacher, but it can augment a teacher.
This way they will verify correctness, good indentation, meaningful naming of variables and so on. Because somebody in the school/government heard that this is what professionals care about.
IMO launching a media campaign which pushes schools to "teach" every child to program, without any plan prepared by professional teachers and developers and then permanent, ongoing support from such professionals, is asking for disaster. And the grandgrand...parent provided an example of such disaster.
People who advocate that everyone should learn to code (like myself) to not advocate the absurd conclusions that are used by others to refute this standpoint.
I do think people should learn to code. This does not mean I think: 1. Everyone should be a professional programmer. 2. "Everyone should be the same"
You can make similar arguments to a person who says "everyone should learn to read," but then you misunderstand the spirit of the discussion.
Careful. That may make you vulnerable to them.
> I don't think this is a particularly logical subject.
Are you sure advocating a solution that's not based on logic is the right thing to do?
> When you say "people" should learn to code, do you mean everyone?
First we must define what "learning to code" is. I (and, certainly, most others) do not advocate kids should learn Java (or Python). But I think kids should learn how to decompose complicated problems into simpler parts. I also think kids would gain a lot if they could make computers do what they want (going beyond "start WoW", for instance).
As for drawing, you can always draw with a pen and paper. I prefer to do it that way. However, if I decided to draw a fractal curve, I'd probably do a few sketches on paper, to grasp the ideas, then fire Emacs and write code to actually draw it.
First of all, why we (adult) do programming? to automate something? to make repetitive tasks easier? or just for fun? and I don't see any good reason, why we teach kids programming. If it's to train their logical thinking, we can make a game for them, give them a basic set of rules, each rules have consequent, with their imagination they can make other rules based of basic rules, with one condition that new rules can't contradict with basic and other rules, I know it sounds like math, but they will get the basic idea of logical thinking, when you do something there is a consequence.
Programming is just a tools or way, if you prefer. Not to mention a new trouble when they have a solution but can't apply it with programming, because the technical barrier they had, even you use easy programming tools like Alice, certainly there will be technical problem for them.
I agree with, why we should learn kids problem-solving skill, because they just need their brain and basic tools like pencil and paper, maybe to scratch something, to visualize what they think.
You create 3d animations using an OO syntax. Like Karel, you build up from basic methods, but you get to animate a scene, rather than have a robot/dog pick up and drop stuff.
My students have really enjoyed it, and it let me get to deeper concepts far faster than other instruction.
edit: http://www.alice.org and it looks like development has actually woken up. The blog is active and there's a new version out. Big improvement over last year when I went there.
I think my main concern with the previous comment is that the dominant method for introducing programming is too syntax-heavy, math-heavy, starting with a language with a lot of overhead for beginners, so ours is an alternative.
Not everyone will like our intro, as you note. But I think it has a very different feel than the way many students are introduced to programming in school (see AP Java class).
The result: to engage as many children as possible, you need several introductory tracks: one that uses math, one that uses puzzle solving, one that uses drawing, one for another common interest, etc. Also be aware of the way interests change with age.
Teaching is hard and almost every approach invented seems to rely on yet another silver bullet.