Papert on the turtle, children and the physical version: https://www.youtube.com/watch?v=BTd3N5Oj2jk
Many today trot out the Poignant Guide, "Learn You A ..." and related efforts as the future of computer education for young people.
I say give them Logo: I was taught by a schoolmarm with no particular programming background in a public school with 20 other kids. I myself didn't have a computer at home but Logo showed me what I was missing by inserting itself into the curriculum of the "new digital economy": driving kids who would have never used a computer to be programmers. The examples and challenges were fun, deep and made writing toy programs a joy.
To this day, Logo seems to crops where I least expect it: A clever t-refplace joke in the pioneering zine "Mondo 2000" (as well as ads for Terrapin), a Larry Wall interview and even my recent toy implementation of the inconvergent tree: http://zv.github.io/algorithmic-tree.html use knowledge I first learned on Logo.
Today, Seymour and Logo are titans, if only to me.
`crtdo` a new turtle in his memory.
Although, The Poignant Guide has a special place in my heart as well. It may not introduce programming amazingly well, or anything, but it managed to transcend the format of tutorial, and stands alone as a fascinating and entertaining read. I didn't care about the ruby: I wanted to know what would happen to the cartoon foxes, and if The Originals would be stopped.
After coming back from something involving a very weak course on programming (You know how they say that you can either teach what to think or how to think? this teaches neither, somehow.), it's wonderful to see in logo, scratch, the Guide, hell, even SICP, a willingness to teach not only how to think, but why it matters, and the joy it can bring (not that I'm suggesting we use SICP to bring in kids. shudders)
Between somebody who learned a bit of Logo, and maybe was given some excercises, and somebody who did the Hour of Code, one of them has a better understanding of what programming is about, and is more likely to see its appeal (hint: It's not the kid who did the HOC).
There's nothing like looking at the screen and seeing something that you made come to life for the first time. And there's nothing quite like being given a problem that seems impossibly hard at first, cracking it, and seeing the result in front of you. It was a magical moment, and though I would not do any more work in logo (UCBLogo wouldn't compile for me), that sense of wonder and magic, and that amazement and the feeling of looking at something, and understanding the complexity that makes it work, and knowing that you designed it, built it, and made it work, that is why I program. For the sheer joy of it.
Thank you Seymour, for everything.