aevaone of the more useful things I realized at some point for how to be a good code reviewer is "that's not how I'd do it" is not constructive feedback and is not a valid reason to request a change, and if you can't think of an actual good reason to block a review, you can save a lot of time for everybody involved by just chilling out about it
side thought: I don't get people who are adverse to reading code written by other people. how on earth did you people learn to program?
Efi (nap pet) 🦊💤@aeva I put my hands in the METABLEND made from all computers ever ground up, powered by the eternal spark of the infinity catalyst
how the fuck did YOU learn to program?
how the fuck did YOU learn to program?
Dan McDonaldI should be clearer.
ANTIC Magazine was, "The ATARI Resource". It had type-in programs, like its peers in other 6502-era machine magazines (e.g. Creative Computing, which touched all of them, and I'm sure there are others but I only know the two Atari ones.) You needed TYPO(2) the program to enter lines with less frustration.
qbasic? I didn't realize there were type-in programs that late in history, but I moved away from the 6502-generation straight into 68k boxes.
Kids... 🤣. (Sorry had to do that)
Type-in basic programs predate the Pentium by 15-20 years.
Look up the 6502 processor, and the late 70s early 80s machines that used it: Apple ][ (][+, //e); Atari 400/800/XL/XE, Commodore VIC-20 or 64/128
Modems topped out 1200baud until 1985...
"It was the 80s"
@danmcd @efi I transcribed old BASIC programs from a book into qbasic without knowing which parts were incompatible, and if something didn't work after I exhaustively checked every line, I think I either tried to narrow it down to things I could remove or moved on to another. The main thing I remember not being compatible were some kind of shape drawing routines, but the memories are really fuzzy. Definitely wasn't a type-in shell.