3 ms·
There are heaps of easy ways for kids to get hooked on programming. Almost arguably too many. The point was, until a comparatively long time had passed, typing
by ggm 3y ago
There are heaps of easy ways for kids to get hooked on programming. Almost arguably too many.
The point was, until a comparatively long time had passed, typing in BASIC was almost ALL Johnny could do. Entire forests of trees were cut down, pulped and turned into numbered line input programs in magazines to play mastermind, tic-tac-toe, table lookup adventure games, or before the modscene was cool, moire pattern b&w interference fringe freak out pop art graphics.
Johnny or Joanna could even be tricked into hard drugs like systems programming a Kansas city standard cassette tape reader and writer, or a new Font. BASIC was a gateway drug.
Kids, if you learned about recursion, don't tell mom.
- OhMeadhbh 3y agoRe-read the article. It's not about how hard it is for kids to learn about programming, it's about how difficult it is to fine a mass of kids who all know the same language and how you can turn on your Commodore 64 and be typing a program 6 seconds later. You really can't do that with any modern system. Heck, it takes 10 seconds for my C64 emulator to load on Android.
- ggm 3y agoI did read the article. My point stands. Because all you could do was program at a REPL a huge cohort of kids learned to program at a REPL. There wasn't a magic algol-68 coding scene at home for a reason: BASIC was what you got when you turned it on. You had to go to punch cards for the other way. There was one lingua franca for kids at home. The shared experience was huge. We've reached a point where deliberately constraints on what a general purpose computer can do might be pedagogically necessary. Much as we give kids cuisenaire rods and abacii when they are small (I made log cabins and ballista with mine) rather than an HP calculator.
- OhMeadhbh 3y agoI think you missed the point. I guess it's hard to explain to someone who wasn't there.