of COURSE this was EXACTLY what we all used our Commodore 64s to do, to balance our budget

also to improve our hand/eye dexterity

Siri, what were the very first RAM addresses we all POKEd


@natecull Anyone who didn't grow up with peek and poke is at a serious disadvantage understanding what computers, ultimately, are about.

@beadsland Yeah, there was something really satisfying about knowing that at the end of the day everything on a computer was all just 'a bunch of same size numbers in numbered slots'.

@beadsland And when your programming language/environment doesn't give you something with the same sort of clean feel to it, you feel... a bit lost and stranded. It's all 'objects', okay, but how big are my objects? What can I put in them? How many is too many? Will they always be there? Do they change when I'm not looking at them?

@beadsland This is probably an argument for C and I wish C weren't evil


@natecull @beadsland My favorite trick in Atari BASIC was that "strings" were fixed-size byte arrays, unlike Microsoft BASIC. And you could make them map to a page boundary by DIM JUNK$(1) and then JUNK2$ by the remainder of ADR(JUNK$) to 256 bytes, and then your memory map. Then just assign strings and use fast string copying to move sprites, or character sets, or draw graphics.

@beadsland @natecull well I grew up with a bunch of Beagle Bros charts and shit and it didn't help me none

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!