my "solver" is really just a super scuffed lisp heavily based around step-by-step processing with the REPL lmao
but given how limited it is and the fact that i'm too busy to write enough utility to make it useful by dec 1st i'll probably just stick to vanilla python
pretty much all the personal project code i've written in the past like couple years has been python lol. jelly and vyxal for golfing and racket, C, and C++ for class, but python otherwise
combine asynchronous processing and redis driven workers for actually processing individual messages and BAM things work great and nmake listservs much more functional than waiting on a never-cleaned IMAP inbox to respond to commands xD
@hyper-neutrino not gonna lie, Python sucks for golfing, but for pure easy readability, ease of learning, and expandability and flexibility for different tasks you can do on it, Python's a pretty good language
@ThomasWard As someone who only really codes for fun, you could've just shuffled the dictionary, chosen some words and put them together, and I'd believe that was something tech-y that you probably do/did :P
yeah I figured that we should stop overspecialising for just fizzbuzz, and start overspecialising for more challenges :p (that's a joke please don't quote this out of context lol)