Jeff Armstrong @jeff@toot.rainbow-100.com

Oops, forgot to mention that episode 92 of the Jeff Reads His Book #podcast is available! Our heroes have a buffet-style dinner! Now that's high fantasy!

https://jeffreadshisbook.com/?name=2020-12-07_jeffreadshisbook_b01_e92.mp3

Finishing up some game dev on a real 1980s #rainbow right now:

https://twitch.tv/fortranjeff

I released my company's internal replacement for Python's buildbot. Built entirely in Fortran, it's designed to replace what we "need" from buildbot. It communicates via #gemini and the titan protocol.

https://git.approximatrix.com/cgit.cgi/levitating/about/

Nothing makes me happier than slapping the always-infuriating JSON License on software I write.

Another shot of the #rainbow screen via video capture

Implemented an inventory window during my Twitch stream today. Not fully functional yet, but a nice addition nonetheless! #rainbow

Let's try some more #rainbow programming...

https://www.twitch.tv/fortranjeff

I'm going to fire up the #rainbow on twitch for the first time:

https://www.twitch.tv/fortranjeff

My #Fortran buildbot replacement is now accepting results from players (build clients) via the titan protocol, and it's all controllable via a #gemini interface.

Too much debugging over the last three days, but clients and servers are now speaking to each other.

I had thought my ancient Bt848 capture card was just a bit crappy when trying to capture a DEC #rainbow video signal, but it turned out the video cable I had been trying just sucked.

I'm rather pleased with my request handling in #Fortran for this build service. The convenience functions for pulling out one path component from the url, all wrapped up in a "request" derived type, is making life easy.

I need to use a graphical client in these screenshots. I think they'd be prettier.

You can now launch jobs on clients from the server's #gemini interface. This #Fortran build service is coming along!

Just to be clear, it builds using any language or runs any shell script, but the clients (players) and server (captain) are written entirely in Fortran.

My #Fortran continuous integration system's server is running and starting to show signs of front-end life, all talking through its #gemini interface (though I do plan to write an http interface).

Server doesn't yet accept API calls from its clients, but we're getting there...

Day 4 of writing a replacement for #python's buildbot in #Fortran. Turns out the database module I had planned on using yesterday was drastically insufficient, and I ended up writing a minimal SQLite wrapper in Fortran.

Now I've realized I need at least a minimal template system if I want web (or #gemini) access. So now I'm writing a basic template engine in Fortran...

It's the morning of day 3 of my quest to replace my outdated #python buildbot infrastructure. I now have a client written in #Fortran that speaks #gemini to communicate with a server (and titan for uploads...).

Moving on to the server side. Not sure which is harder to write yet.

Well, buildbot 0.8 can’t install on my M1 Mac, so it’s finally time to move on to another continuous integration system. They all seem so heavyweight, though. Might be time to write a simple one...

I hate the AI hell world we live in...

After hunting down a major indexing error in the code, players can finally interact with signs in my #rainbow game!

Caught myself putting "PgDn" and "PgUp" controls in a #rainbow game... Rainbows have "Prev Screen" and "Next Screen" keys, not that IBM nonsense.