3 ms·
Somethink I never think about: "It wasn’t always that easy to develop a program and run it on the same machine" Really? Of course I'm not talking about embedde
by anta40 3y ago
Somethink I never think about:
"It wasn’t always that easy to develop a program and run it on the same machine"
Really? Of course I'm not talking about embedded system. But PC in the 70s/80s, like Apple II, ZX-80, TRS-80 etc etc.
I guess we, 90s kids, are too spoiled :)
- mysterydip 3y agoI've been reading the ZX Spectrum Visual Compendium from Bitmap Books (https://www.bitmapbooks.com/products/sinclair-zx-spectrum-a-visual-compendium https://www.bitmapbooks.com/products/sinclair-zx-spectrum-a-...) and it has a lot of developer anecdotes in there. One of them (Clive Townsend) was talking about their development process: "The original Saboteur! code was written on an actual Spectrum so everything - the source code, assembler program, and object code - had to be in memory at the same time. I'd work on a routine, compile it, then save it. To test it, I'd reset the Spectrum and load the newly compiled routine along with other necessary code, graphics and data. After testing, I'd reset the Spectrum again and re-load my source code and the assembler program. All from cassette! Nightmare!"
- ikari_pl 3y agoSometimes you could have something plugged into the extension port to snapshot the memory, so you can switch easier, AND not lose your changes. It sounds horrible NOT to have it when writing a game like that (I love Sabouteur! Spent more time playing the 2nd part :))