I can only speak from my own experience, so I don't know if this holds for everybody, but I think the guy misses a lot of important points. When I was 13 I dis

I can only speak from my own experience, so I don't know if this holds for everybody, but I think the guy misses a lot of important points. When I was 13 I discovered programming, using QBASIC, on my old 286. This was in 1993, before the Y2K and .COM hoopla, and before anyone I knew had access to the internet, or even knew what the internet was. Back then, if you went to the library by my house, they had about 2 books on programing, from 1982, that had nothing more exciting in them than "this is how your draw a maze in BASIC on your Apple II". Every now and then you might be able to find an old issue of Compute, with some code samples in it. For the most part, however, there was a pretty large dearth of information about programming accessible to a 13 year old kid who didn't know any one who knew anything about programming. The thing I did have, however, was a copy of nibbles.bas and access to the QBASIC help screens. The language was small enough that one kid could read through every item in the index, and figure out what the meant. There were a few things, like BLOAD and BSAVE that I couldn't understand because I didn't know what pointers were or how they connected to arrays. Other than that I was able to figure everything out by just reading through the help screens. This, I believe, is what made BASIC suitable for use by kids. It wasn't complicated. There wasn't a vast class library. The ability to produce sound was limited to the PC speaker, and there certainly wasn't any 3D graphics. There wasn't a windowing system, or any kind of scheduler. BASIC certainly didn't have huge libraries to import. Everything was super simple. That made it approachable. It was something a kid could explore by him self, understand, and appreciate. When you are exploring computer programing, writing apps that play pong or let stick figures shoot at each other with laser guns, all the rules on the right way of doing things just get in the way. They keep you from having fun. All you really need is a few variables, SCREEN, CIRCLE, LINE, BEEP, COLOR, and GOTO. You definitely don't need classes, fields, closures, while loops, or even proper indentation. That stuff doesn't add to your DISCOVERY of computing. Yes it makes you a better programmer, but with kids that shouldn't be the goal. The goal should be to HOOK them on programming. Rules just get in the way. Python has way too many of them. A lot more than BASIC. Python has to be taught. You have to teach people: use control structures, indent your code, model things with objects, import these things. That makes it great for, say, college freshman, or AP students. It's not really suited for kids though. BASIC can be explored. Easily. You can hold the entirety of BASIC in your head, at once. Everything. You can't do that with python, or even lisp (because of all the libraries). So I say, give kids basic, and let them roam free for a while. Let them make laser games out of spaghetti. I think sometimes its easy to forget how much fun it was to write crappy spaghetti code that did small amusing things. Think back to when you were a kid, before you were old enough to know better. That's probably what got you hooked. Its what got me hooked. That means BASIC, or something like it. You have to let people be creative, and messy, long before you start throwing rules at them. You can teach kids structure, and recursion, and pointers, and all that stuff later.