I'm saying, so long as you want to encourage X, why not directly take the steps to encourage X?
That being said, I'm not entirely convinced this is still a good way to teach coding.
Of course, you're perfectly free to set up your own project using Squeak. I bet you'd get a lot of people onboard with that. Then you can prove me wrong :)
But first we need the code. Then we can figure out what to do with it :)
I think that's even more accessible and tweakable than a system where the source code is 100's of keypresses away.
Of course, everyone learns differently. I could certainly be way off base. But I bet most people who actually did those code listings would agree that there's a certain value there that's very hard to reproduce with view source and cut+paste.
Yes, but instead of getting kids into doing by forcing them to type, I think it's much better to just make the source accessible and encourage them to tweak.
You may not know this about Smalltalk, but not only can you browse the source code of everything quickly, you can change it and have those changes active instantly on a key press. In fact, the whole thing was specifically designed as a digital Montessori toy for kids.
I think forcing today's kids to type in source code will just be seen as unnecessary drudgery. If doing is what we want to encourage, why not just make it easy to do and provide some guidance in that direction?
Thanks for starting this — all this talk of closed systems keeping kids from playing with programming, and whether video games/programming was art or not was distressing.
http://www.squeak.org
Edit: To encourage kids to tweak and program, make the source easy to get to and a breeze to modify. Forcing them to type The whole program to do this strikes me as a bit indirect. We did it in the early 80's because we had to. Often, there was no other way to get your hands on that particular program. Today's environment is vastly different.