Show newer

Get your conspiracy theories ready, I've run into problems using set! on powerpc-linux.

@cwebber You can't tell a variable what to do, they're free.

<examines documentation for set!>

Ah, I was mistaken. You can tell them what to do.

@cwebber shareware variables

Free until you use it 10 times, but then it's $10 for a lifetime license.

@cwebber still closed userspace and the target is datacenter use for non-graphics

"There is code in there to support display, but it is not complete or fully tested yet."

Thanks to the wonderful @milan and his , our will be streamed live on PeerTube!

Saturday, May the 28th, CEST timezone:

14:00 - Real Solarpunk Technology

15:45 - Empowering Future Communities

17:30 - Is Solarpunk Just Another Style?

19:15 - What's Holding Us Back From A Better Tomorrow?

become the cheap special effects transcendent space cloud being you want to be


@cwebber closed (local to the Let-over-Lambda), passed in (to the fn within the LoL), or ambient/free (defined outside the LoL but in the same or parent scope as it, probably a source of bugs if mutable)?

@cwebber Let's found the National REPL Association, to defend the right to own and use footguns interactively.

free because you're not in the closure, not enclosed, now I get it *nods head solemnly*

Show thread

@cwebber Not necessarily in languages with dynamic binding. There you can have true freedom (to shoot yourself in the foot).

"free variables" always confuses me, like how free are they? they're bound somewhere else before you even get to the closure you're looking at

Show older

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!