4 ms·
Yeah, but you won't learn to program from OCR. (I credit typing in listings for about 80% of my initial learning).
by flir 3y ago
Yeah, but you won't learn to program from OCR.
(I credit typing in listings for about 80% of my initial learning).
- NoZebra120vClip 3y agoCompute!'s Gazette was my "GitHub of the 80s" for my Commodore machines. It was absolutely a wild ride, typing in programs from the back to do everything from games and word processing and who knows what. IIRC, they began with BASIC, but then they essentially bootstrapped a foolproof, checksummed machine-code editor and, somewhat regrettably, cut out the source-code middleman. The punchline is that I did not necessarily have any way of saving those programs to persistent storage, so it was just like... keep the computer turned on for a week? Most coders learn so much from hacking on other people's code, it's an indispensable step. So typing in code is a great opportunity to experience coding, starting with a working codebase, and perhaps making your own tweaks, fixes, and enhancements. Commodore BASIC was perfect for rapid prototyping and access to sound and graphics primitives.
- u801e 3y ago> then they essentially bootstrapped a foolproof, checksummed machine-code editor I remember that I copied a short program in BASIC that you had to run in order to type in the machine code part of the main program you were typing. It would sound a bell if the checksum had no error, otherwise you would hear a buzz sound. > and, somewhat regrettably, cut out the source-code middleman. The programs I typed in had parts in BASIC and other in machine code. I just wish the machine code parts used the instruction mnemonics instead of the actual instruction byte code. It definitely would have been more educational to see instructions like LDA, SDA, CMP, JSR, etc instead of the actual number values.