5 ms·
"I admitted that generally, school was hard for me, but I loved art..." Logo. He should have taught them Logo.
by pmoriarty 10y ago
"I admitted that generally, school was hard for me, but I loved art..."
Logo. He should have taught them Logo.
- spaceandshit 10y agoAgreed. I was taught Logo in the 4th grade and it was a great introduction into programming and computers, which ultimately led to a stronger foundation in the field.
- voltagex_ 10y agoI probably picked Logo up around that time too. I still dip into it from time to time. I just wish there was a good JS implementation that I could run in the browser - you never know when the urge to draw spirographs will hit.
- ido 10y agoI was taught Logo at the 4th grade and it seemed pointless to me cause you couldn't make games in it...I know now you probably could, but they only showed us how to make the turtle draw simple things, basically a recipe to draw a house etc (QBasic was the holy grail at the time, then Turbo Pascal). I guess tho the main problem was that few primary school teachers in the early 90s actually had even basic programming competency. The only ones I knew who could do any programming beside the trivial textbook examples were other pupils.
- dagw 10y agoLogo is what got me interested in programming after failing to see the point of BASIC.
- sundarurfriend 10y agoWhat do you folks think of Scratch? I see a lot of excitement around it, but after trying it, it felt like even 10 year old me would have preferred the unconstrained freedom of Logo over the weird assemble-these-blocks environment of Scratch. But then, perhaps introverted nerds who loved play-doh over LEGOs are not the best sample set to extrapolate from.
- myhf 10y agoI've tried several educational programming environments for a semester at a time, and Scratch is by far the best for students too young to type. Logo and Processing are nice for slightly older students. It's not immediately obvious, but Scratch is very very good at some important things for education. Loading, saving, and starting the editor are fast even on slow machines. When things go wrong, they don't stop the rest of the program. And concurrent programs are easy to write in a wide range of styles because multi-frame loops run at exactly the same speed for all scripts. There are a lot of imitators that improve on Scratch's weaknesses by adding first-class references to lists, sprites, and functions. Or integrating a physics engine. Or binding directly to Minecraft or Sphero. But if they are slow to load or execute, you can't iterate as many times in an hour of class. If errors demand time to troubleshoot, that attention comes out of the rest of the class's instructor time. If you are limited to only one way of writing concurrent processes, it might not be a style that fits well with a particular lesson. I hope that the ongoing HTML5 port of Scratch gets the same things right.