2 ms·
I separate "power on to" and "BASIC". In my view, Python, is the language closest to "BASIC done right," so I am interested in "power-on-to-Python". In classic
by yetanotherfrank 8y ago
I separate "power on to" and "BASIC". In my view, Python, is the language closest to "BASIC done right," so I am interested in "power-on-to-Python".
In classic "power-on-to-BASIC," the BASIC interpreter was a single shell that allows interactive instructions, OS commands, and editing (with line numbers). Even to run a game, one needed to know and type at least one BASIC command.
Python's shortcoming here is that one cannot easily run Python programs from inside the Python REPL. Check out this silly attempt at Python with line numbers and a READY prompt...: https://github.com/frankseide/basicpython https://github.com/frankseide/basicpython
The big difference between a Python IDE and Scratch (and similar GUI-based systems) is that Scratch is a top-down approach that start with high-level objects/operations and gradually give access to more and more details. On the other hand, the classic BASIC computers, and a Python system, are bottom-up. Those would not allow self-written games to be flashy from the start, but on the other hand kids would gain a much deeper understanding since they have to build things up themselves.