Starting over, but with Guile. Because when your learning curve is already quadratic, doing it twice isn't actually a problem

Pros: Using Guile is more obviously like functional patterns in Lua than Racket is, and bindings to C are right out there

Cons: The documentation does not spark joy and, at this point, it's less obvious how much work the type system is going to do for me

@AbbieNormal Gnu documentation tends to reference other docs and may assume familiarity with Gnu as a whole. At the same time, there's often polemics rehashing core Gnu values to skip through before one gets to the meat of setting up and using the software. This creates situations where information necessary to setup and use the software documented doesn't begin until chapters 2-4 of the basic docs. It's also difficult to identify the core document for a use case, especially at entry level

Then there are minor navigation issues like the next link disappears when there is no sibling to the right, so the reader must go up to the parent then next. Also reading by navigating with next, et al., hits different URIs than what are in the table of contents so you can't tell what you've already read when you look at the ToC

@alcinnz @ekaitz_zarraga
I thought you just give the dragon book a once through and you're good to go 😂

I've decided to learn #Racket and DSL development in Racket then backport some of those languages to a C/Lua Stack as an extension of the Lua philosophy of avoiding premature optimization

OCaps shitpost

@casastorta @codewiz Perl 6 is called Raku, for reasons

@ekaitz_zarraga You should look for RISC-V or decentralized software grants

@ekaitz_zarraga 🖕FULOL 😎😂

@ekaitz_zarraga "I have ideas on the toilet, too"