#lispyGopherClimate #technology #programming #show
https://communitymedia.video/w/wQkFYMbzbvBkpYLt1tWMZB #archive
- @wm_annis reports an sbcl merge of slop (EDIT: REVERTED v) unlike #ecl viz @jackdaniel . #commonLisp
(#clisp)
Individual heterogeneity
- in #climate activism
- in the #gopher
- in The #Lisp Community
- My idea of sharing conditions/handlers rather than programs
Cf the fully intended homogeneity from LLMs.
- yduJ is square dancing this week, as all lisp users must.
I updated my post "Do I need a Lisp Machine comeback?". I have added the new information I've found with chatting with folks on lisp IRC channels.
https://far.chickenkiller.com/computing/do-i-need-a-lisp-machine-comeback/
Seems like I was looking for was "residential style development" or something. Dunno yet what does it mean. But for sure I am digging something out of grave!
#lisp #lispmachine #interlisp #residentialdevelopment #development #softwaredevelopment #programming #commonlisp #clisp #cl #computing #computers #retrocomputing #wakegp #research
One might say I’m too obsessed with Lisp. Or in general with “unconventional” things. Maybe I am. Or maybe dead technologies have got some buried gems which you cannot find in the modern world of computing. This story is about WakeGP. Few years ago, I wanted to start with Evolutionary Machine Learning, specifically Genetic Programming. So I started writing WakeGP software using Rust. And it’s been few months which I’m doing experiments using different parameters and algorithms to see which ones produce better results(e.g. better accuracy).
#programming #workflow #GUI #mcclim #commonLisp #emacs #ecl #clisp #slime #leonardoCalculus #eepitch
https://screwlisp.small-web.org/lispgames/LCKR-object-oriented-simulation-simulation/
I have to say, I am really, really happy with how the flow into the thirty second GIF reflects my ideal computer useage.
Basically, I write a clim command that steers my leonardo system "like a person does" via emacs-server, visible in the background of the straightforward clim interactor GUI I generated in a couple lines.
CL packages are the wrong way to implement packages in Lisp. As I explained in a discussion two years ago, packages implemented using obarrays (or equivalent) don’t work reliably.
We have a much better basis for Lisp packages in the shorthands mechanism. It only needs to be completed.
Richard Stallman on CL packages landed
#clisp #emacs
https://andreyor.st/posts/2022-11-01-emacs-lisp-shorthands-as-namespacing-system/
> The reason namespaces systems do not fit well into #Lisp is that they have to operate in ‘read’, in the choice of which symbol object you get.
Richard Stallman on Emacs Lisp's future
In Emacs version 28 Emacs developers introduced so-called read symbol shorthands. If you’re interested in the rationale, feel free to search the Emacs developer mailing list for the discussion. However, it does seem that not everyone likes the idea of shorthands as a substitution for namespaces (or packages, if you’re coming from Common Lisp).
@lxsameer that's cool! I *recently* started using #emacs because I found file navigation annoying in other IDEs. I know how to touch type, so now I literally just have to type in what I want (with all the autocompletion benefits just like a shell). Still learning the basics but finding even that awesome!
By the way, I've been programming a bit of #Clojure too, although right now I prefer the #clisp vibes 
clisp -modern -E UTF-8
#clisp #commonLisp #lisp #localisation #youCouldHaveHadMyZorkmids
Bloody well written ..
https://nyxt.atlas.engineer/article/elisp-vs-common-lisp.org
screwlisp
Farooq | فاروق [Master Patata]
Gene Pasquet
Alfred M. Szmidt
HoldMyType
Hippo 🍉
vintage screwlisp account
unixbhaskar