शून्यता
Lispy Gopher Climate w/ screwlispPublic Lispy Gopher Climate sunday Morning in Europe stream - 3/22/2026, 8:00:19 AM
The #Nimble type inferencer required about 30 seconds to type the #TAK function given above on a 4 Megabyte #MacintoshPlus with a 16MHz 68020 accelerator running Coral #CommonLisp. (h g b)
PeerTube
Hacker News
screwlisp#itchio #gamedev #programming #theory completely explainable game-embeddable #deepLearning system using #roc #statistics .
I coded this one simply and iteratively, since a few people worked on reimplementing my #commonLisp code to-be-simpler.
The gist is that I show that deep learning updates, and indicate training as well are a simple true-positive/true-negative/false-positive-false-negative equation of the previous time step in an eminently explorable way. #DL #AI
charliemacI plan on streaming #McCLIM and #OpenGL things in approx. 90 min from this post time, 2026-03-20 12pm CDT/ 17:00 UTC.
https://www.twitch.tv/endparen
I plan on testing out the just-merged input-editing work from upstream and working out some of the remaining bugs with the text atlas using the mcclim-truetype backend. It would be great if I was in a place to start on the SDF side by the end.
Paul SomeoneElseMy new task tracker is done enough to use:
https://not.d34d.net/
*** It kinda looks like it is ready for public use, but
it is not. The register/reset/login flow is not hooked
up yet.
Here is the code:
https://codeberg.org/pkw/chicken-web
It is basically a scheme copy of this common-lisp project:
https://codeberg.org/pkw/clue
There was no reason to rewrite it besides I wanted
to do it in scheme. I think I learned more about both common-lisp
and scheme, and would still highly recommend either language
as very good, thumbs up emoji !
I used a copy of the sqlite file to develop then new one.
I like how I enrcypted a small piece of info into the session
cookie that the server can decrypt.
(The cookie should be mostly useless and contain no data.)
*** If you don't get what this offers over say Flask ...
You are correct, it offers nothing except it might be more
performant and have less cultural complexity.
#chicken #scheme #commonlisp
https://not.d34d.net/
*** It kinda looks like it is ready for public use, but
it is not. The register/reset/login flow is not hooked
up yet.
Here is the code:
https://codeberg.org/pkw/chicken-web
It is basically a scheme copy of this common-lisp project:
https://codeberg.org/pkw/clue
There was no reason to rewrite it besides I wanted
to do it in scheme. I think I learned more about both common-lisp
and scheme, and would still highly recommend either language
as very good, thumbs up emoji !
I used a copy of the sqlite file to develop then new one.
I like how I enrcypted a small piece of info into the session
cookie that the server can decrypt.
(The cookie should be mostly useless and contain no data.)
*** If you don't get what this offers over say Flask ...
You are correct, it offers nothing except it might be more
performant and have less cultural complexity.
#chicken #scheme #commonlisp
Going from #commonlisp to #scheme is a great way to lisp level up.
(I would guess going from scheme to common-lisp would also be
a great perspective shift.)
My take so far is that common-lisp is more practical, but also
clunkier and more verbose.
Like I miss CLOS when I am handling things that follow a
pattern but are distinct. Like handling forms in http/html.
But in scheme the advantage is it is easier to just be way
more dynamic and meta where it's needed.
I would be happy in either, and I stand by my earlier
take that a team project on common-lisp would be
great, and scheme is nice as someone solo that
can do complex stuff fast and seemlessly.
(I would guess going from scheme to common-lisp would also be
a great perspective shift.)
My take so far is that common-lisp is more practical, but also
clunkier and more verbose.
Like I miss CLOS when I am handling things that follow a
pattern but are distinct. Like handling forms in http/html.
But in scheme the advantage is it is easier to just be way
more dynamic and meta where it's needed.
I would be happy in either, and I stand by my earlier
take that a team project on common-lisp would be
great, and scheme is nice as someone solo that
can do complex stuff fast and seemlessly.
My grandiosity crept in while I was trying to convey that I am pretty sure I am pretty onto something.
Anyway, this is part 0 of my #itchio series on my #deepLearning by receiver operating characteristic #statistics #dl #roc #DLROC implemented in pure ansi #commonLisp based on the condition system.
Time 0:
> Sharks.
Time 1:
> Feed sharks humans.
Time 2:
> Feed sharks.
It is very enlightening for me personally.
It is a bit early, but I hope *you* participate with it.
Game-Emeddable small Deep Learning (-assets) are a Receiver Operating Characteristic Part 0 - DL-ROC.LISP by screwtape
To say the ending first, look at this tiny deep learning inference, where I have embedded symbols in literally the same gold standard (“training data”) of my early article https://screwlisp.small-...
λzydThink I managed to rip out all the remaining slop from SBCL's 2.6.2 release. Builds on Linux x86-64 so seems fine for me™. Probably going to use this personal fork for the foreseeable future. Might try to update it to future releases but depends on the complexity and amount of slop.
(Stainless) Steel Bank Common Lisp: https://codeberg.org/zyd/sbcl
The name is very cute, admit it.
Kent Pitman on Technology, LLMs, AI, the environment, MOOsaico, and LambdaMOO + #lispyGopherClimate
