I just love this way of sharing software, not sure why, because it seems super tedious to write 20 pages of line numbered basic, but in the same time it seems freeing, as you can change it as you write it, and the interaction between the user and the program seems very intimate.
Maybe if we went the lisp way this would've been more possible to just change the software you use, kind of like pico8 (https://www.lexaloffle.com/pico-8.php) where you just hit escape and you can edit the lua code.
Somehow personal computing became not personal at all.
I learned programming from these magazines. It's the ultimate open source, as the code was generally small enough that you had a shot of understanding every single line. Sometimes the code listing was documented in the article, which explained how the implementation worked, rather than just explaining what the application does.
The Japanese did these "type-in" source code listings really well, much better than I saw growing up in England. They eventually adopted entering complicated listings as hex code with checksums, which was both faster and less error prone but of course less readable. The bootstrap code would spit out the line where the error was when the checksum failed and you could easily correct in small groups.
I didn‘t have a C64 when I was growing up, but I think there were a lot of magazines for the C64 with code in their issues and I imagine it must have been thrilling to type it out and understand it in the process.
Things like that were in my dad's PC magazines; I tried to do it once when I was a kid, unsuccessfully of course because I had no idea what I was doing.
Maybe this guy's work is still floating around somewhere. Here's a retro art gallery with a mix of east and west: https://tomseditor.com/gallery/browse
btw... The first one there is a NEC PC-9801VX(0/2/01/21), but the drawn model number looks more like MX (doesn't exist) or UX (look different). The notebook's single labeled dial means it's probably a PC-9801NA/C. The X68000's graphics tablet might be a Wacom UD or UD II with a stylized menu strip. Its monitor is a Sharp CZ-60(6/8)D. The misplaced indentation on the X68k's second tower is an error.
"From LOGiN 1987 No 5, the story of 篠原賢 Kenichi Shinohara who "for something to do" at the age of 60 years old began using an NEC PC-98 to draw pixel art reproductions of Ukiyo-e and printing them as folding screens and kites!"
Depends where you want to place the emphasis. "Pixel Art Ukiyo-e" places the focus on the primary medium being pixel art, and it's use to recreate ukiyo-e. The other way round is equally valid but changes the primary emphasis to Ukiyo-e, which was undesirable for me.
Pixel art is a style that can be produced across many mediums, and Ukiyo-e is a medium that can accomodate a variety of styles. So a replication of Ukiyo-e art on a screen isn't actually Ukiyo-e anymore than a print of a Van Gogh painting is actually a Van Gogh painting.
There is a link to the article LOGiN magazine from 1987: https://archive.org/details/login-may-1987/LOGiN%20-%20May%2...
Around page 318 you can see some games https://archive.org/details/login-may-1987/LOGiN%20-%20May%2...
I just love this way of sharing software, not sure why, because it seems super tedious to write 20 pages of line numbered basic, but in the same time it seems freeing, as you can change it as you write it, and the interaction between the user and the program seems very intimate.
Maybe if we went the lisp way this would've been more possible to just change the software you use, kind of like pico8 (https://www.lexaloffle.com/pico-8.php) where you just hit escape and you can edit the lua code.
Somehow personal computing became not personal at all.