It's consuming me because at long last I'm *able* to. There's docs, disassemblies, & reimplementations in easy reach now.
Cis reckon
When my daughter was hitting adolescence i was hit with this profound melancholy and mourned knowing I’d never again see that little kid i loved so much, and she was becoming someone else whomst i also live but was changingg into someone new, as we do when we grow
So when she told me she was a girl i was like u got it babe
when i hear about parents of trans kids mourning or whatever im like, you mean you havent dealt with the ephemeral nature of being until now??? Basic ass scrubs
In 1989, I got a well-used copy of the Official GEOS Programmer's Reference Guide (which I call OGPRG) & geoProgrammer. Due to critical errors in OGPRG & sample source code files, I've been wanting a single reference as complete & correct as the C64PRG ever since, knowing the only way I'll get one is if I write it myself. I've wanted to for 30 whole years. Now it's consuming me, & when I'm done I'll probably know the OS inside out.
Bil Herd, the 128's designer, gave a talk in '16 about what it was like inside Commodore during the second of its "tragedy in three acts." https://www.youtube.com/watch?v=-Zpv6u5vCJ4
There are also times when I really like the CLI and the power of shellscripts. Last night, I spent about 5 hours hand-drawing just a few technical pictures in gimp 6x each because I didn't like how they turned out. Today, in about 5 hours, I wrote and debugged scripts using ImageMagick and a short text file to draw 34 pictures for me, and to write a whole HTML table of data (including ASCII art) to go with the pictures besides.
Specifically, "while" loops on the receiving end of a pipe. Variables are local because the loop is executed in a subshell. Oops.
There are times when I really question my choice to do things in shellscript. Did you know that in BSD /bin/sh and in Bash, variables inside "for" loops are global like normal, but variables inside "while" loops are automatically local to the loop? I didn't, and I wasted about an hour fruitlessly debugging everything because of it.
The picture I commissioned of Maffi is done!!! It looks amazing and I'm really glad to have better art of her now.
This ✨ sparkly shellscript princess ✨ spent her weekend writing a shellscript to convert numbers from one base to an intermediate representation to another base. The result is the most uselessly useful shellscript I've written in a *very* long time, a script to convert a conventional date into a Rickdate string: https://thornton2.com/rickdate.html
Pictured: my sense of accomplishment.
I may have found one, & I'm almost kicking myself. cc65 has a symbol table lifted from the Hitchhiker's Guide to GEOS, checked only for fidelity not correctness. But it also uses a few include files for cross-compiling Apple II GEOS programs, which means conflicting addresses *had* to be resolved: https://github.com/cc65/cc65/tree/master/libsrc/geos-apple
Back in the day, GEOS was so popular that (by one account at least) nearly half of all C64 owners used it. GEOS 128 didn't quite reach the same status but it was still a bit respectable. The Plus/4 & Apple II versions, however, never made it out of obscurity.
✨ Kind 'Net Help Desk fairy by day. ✨
✨ Weird & furry Unix fairy by night. ✨
✨ Sometimes a retrocomputer fairy. ✨
✨ Pays the ComputerFairi.es bills. ✨
✨ Sparkly✨shellscript✨princess. ✨
✨ Age: Mere days younger than ✨
✨ the Intel 4004 & Unix 1st Edition. ✨
✨ Follow requests welcome. ✨
✨
✨