buc.ci is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Hey y’all, need a seasoned Lisper and #Web magicker? I need money to properly open a bar, so some contracting arrangement would be really nice. My CV is at <https://aartaka.me/cv.html>, at the same domain as all my writing and many projects <https://aartaka.me/>. Open to remote, because the bar’s in Armenia. Any spectrum from full-time to hourly pay is fine as long as I do decent things to the world on weekdays and get to serve drinks on the weekend. Hit me up!
#getFediHired #fediHire #Lisp #Scheme #Clojure #JavaScript #WebDev #SoftwareEngineer
Let Over Lambda is free to read online now, apparently https://letoverlambda.com/index.cl/toc
Somtimes I think that the lack of ML-like types and modules making it harder to do top-down design in Lisps.
https://paulgraham.com/progbot.html
https://thunderseethe.dev/posts/ml-modules-for-mere-mortals/intro/
Lem editor: "a modern #emacs ?" quick tour (7 min): https://www.youtube.com/watch?v=Y5mo4FpatB8
ncurses & webview (SDL3 and WASM coming), dashboard, multiple-cursors, file tree, directory mode, markdown's multiple major modes, transient pop-ups, Git interface, upcoming Org mode…
and yeah I lost access to my previous channel, thanks Google's verification process.
HP 200-LX running #lisp in the old NSA listening station on Teufelsberg. #retrocomputing #programming #vintagecomputing
Let Over Lambda—50 Years of Lisp by Doug Hoyte, the book on macros and advanced Common Lisp inspired by On Lisp, is now free to read and download.
The Lisp curse, now coming to your ecosystem
https://javahippie.net/programming/llm/2026/03/05/the-lisp-curse-coming-to-your-ecosystem.html
The Lisp Game Jam is happening, and yes, @spritely is participating again this year! https://itch.io/jam/autumn-lisp-game-jam-2026
The Lisp Game Jam is a no-genAI-permitted game jam.
If you want to get started, may I recommend Spritely's Hoot? We even have a game jam template with a mini-breakout game for you to try https://codeberg.org/spritely/hoot-game-jam-template
Have fun! Look forward to seeing what you make, no matter how big or small!
@eclecticpassions @amin @nantucketlit @hyde @thorstenzoeller @birming @gumnos @ed1conf
#EMACS (escape meta alt control shift? XD) is crazy powerful, especially if you're into #Lisp, but for me, modal editors like #vi (and #ed) are where it's at. ;)
P.S., Syntax highlighting = overrated, but man, but I do m
iss proper wordwrap at times!
(vim has it, though)
Aight mastodon I need some help coding.
I wanna make a simple webserver and I got to the point of sending a favicon after loading the page and just can't figure out how.
How do I send an image file in a webserver written from scratch in common lisp?
Using the USB serial support in the bare metal Genera port to talk to a Taylorix S4 which runs a custom FORTH port with a disk backup/restore and floppy formatting tool. #forth #lisp #cpm #retrocomputing
What's a good lisp that I can embed in a Zig application that is permissively licensed (BSD-like)?
I really miss working in Clojure, but as far as I know there's no embedded version and I have no desire to ever be stuck using the JVM again, but it's the only one I even sort of remember. Other stuff I'm finding I have no good way to evaluate the pros and cons, so I'm seeking personal recommendations (and why it's the right choice, please!) instead.
As part of my ongoing history project, I am checking hardcopy documents I have against online archives to try to notice when things I'm forced by circumstance to get rid of are available from some other source.
I noticed web pointers to something called the Lagout Museum [1], which was a web site that had a lot of old computer documents, but in particular some Symbolics lisp machine documents. It's gone now, so I was getting 404s. But I found it on the Internet Archive's amazing Wayback Machine [2].
Sadly, it's a pain to browse because the historical artifacts [3] contain code that pops up a prompt for donations. So, always up to a challenge, I used my netsettlement git(hub) repo to host a browsable mirror of the directory structure (not the actual files) that does not have the pop-up menu problem.
It's better explained in the README.md at https://github.com/netsettler/netsettlement/blob/main/symbolics/lagout_museum/ for more details.
[1[ Original home of the Lagout Museum (https://lagout.org)
[2] Internet Archive (https://archive.org)
[3] Internet Archive backup of The Lagout Museum (https://web.archive.org/web/20251010122927/https://doc.lagout.org/science/0_Computer%20Science/0_Computer%20History/old-hardware/symbolics/)
#KentsHistoryProject #Lisp #LispM #LispMachines #Zetalisp #Symbolics #RetroComputing #InternetArchive #WaybackMachine #LagoutMuseum
SRFI 269: Portable Test Definitions is finalized.
Yeah, it's final! It won't change anymore! :)
1.5 years of work, dozens of interviews and talks, hundreds commits, thousands of words and LOCs.
Now people can start adapting it. In the meantime, we will post articles, make stream and videos.
https://srfi.schemers.org/srfi-269/
The most suitable implementation is `suitbl`, of course.
https://git.sr.ht/~abcdw/guile-ares-rs/tree/master/item/src/guile/ares/suitbl
My deepest gratitude to @nlnet and @NGIZero for funding this work! 🫶
What makes Lisp difficult to read?
https://paultm.nl/paren-thesis
Comments: https://news.ycombinator.com/item?id=49879343
#HackerNews #Lisp #Difficulty #Readability #CodeChallenges #Programming #Language
@h4ckernews Nothing at all. Of all computer languages, #Lisp is the most regular and thus easiest to read.
@asllop @h4ckernews To be entirely fair, many programming languages strive to be 'English-like', making them possibly easier for anglophones to learn.
#Lisp does not do this: it is unambiguously a foreign language, one which needs to be learned. There is a learning curve. It's also a dense language which expresses a lot compactly.
As you say, comprehensibility is at a level somewhat above the actual implementation language, so is not especially a matter for this discussion.
Good point.
Just to stake this out until a better suggestion arrives 🙂:
(defmacro omelet ((&rest vars) &body body)
"Octolinear Macro-Expanded LET."
(let ((vars (mapcar #'(lambda (v) (etypecase v
(symbol `(,v nil))
((cons symbol (or null (cons t null))) v)))
vars)))
`((lambda (,@(mapcar #'first vars)) ,@body)
,@(mapcar #'second vars))))
Preparing the variable list with `loop' and `collect-into' instead of `mapcar' is left as an exercise.
Traveling OSM Salesgirl Problem ✊🏳️🌈🏳️⚧️🇺🇦🇵🇸 [she/her or any neopronouns] » 🌐
@contrapunctus@fe.disroot.org
I really wish people who criticize/hate on #OOP would specify whether or not they have used CLOS (the #CommonLisp Object System).
«the #Lisp family of languages, and particularly #CommonLisp, ... at least at a conceptual level, ... did so many things right really early on»
But Lisp started _very, very early_ on.
A lot of things in Lisp weren't right for the first ten years or so (at least).
Of course, it could hardly be otherwise, since doing things right requires an accumulation of experience and those who came first had nobody to borrow that from.
Function or macro?
Yet another very short and simple answer for (Common) Lisp.
A macro, if and only if it must do its thing at compile time;
otherwise, a function.
that books gets some stuff right and some other stuff wrong. But it is definitely worthy to read.
For instance, #Lisp and Lisp machines(#LispMachine) have many features which you cannot find in tons of languages today. Includes the classic language of #Unix, C.
See these blog posts:
https://far.chickenkiller.com/computing/do-i-need-a-lisp-machine-comeback/
https://www.marginalia.nu/log/53-better-hard-drive-metaphor/
Proposal of contributing guidelines in #ecl: https://gitlab.com/embeddable-common-lisp/ecl/-/merge_requests/389
Includes project LLM policy.
Yes, it is more complicated than that.
In addition to the above, I'd say "unfortunate", rather than "poor", since these matters were not understood in 1958 and then later only Scheme could afford such an incompatible change.
Moreover, any problems with Lisp-2 are minor as language design problems go.
@vnikolov @screwlisp @kentpitman @nosrednayduj Portable Standard #Lisp and #InterLisp are both also #Lisp1. There are equally good historical reasons why #CommonLisp should have been Lisp1 as Lisp2, which is why we had such a big and bruising fight over it back in 1986.
I was on the losing side; I do think the decision was mainly political, not technical.
For someone doing higher-order programming, there is the minor annoyance of having to write sharpsign-quote and `funcall', but that is far from maddening.
@mdhughes @simon_brooke @screwlisp @kentpitman @nosrednayduj
@vnikolov @simon_brooke @screwlisp @kentpitman @nosrednayduj For a "lambda calculus" language to make passing around lambdas a little splinter in the finger every time, is not ideal. Especially when we see that it *can* be splinterless, the splinters were deliberately chosen!
#lisp #scheme #commonlisp
I love the cover of this 1972 TENEX manual of BBN Lisp from which Interlisp originated. In addition to featuring the parentheses of Lisp the cover nods to square brackets, the superparentheses that would become a staple of Interlisp syntax.
https://www.bitsavers.org/pdf/bbn/tenex/TenexLispRef_Aug72.pdf
Anyway, there are some issues with AI development in Rust:
https://codeberg.org/ethical-foss/open-slopware#programming-languages
#faircamp #kiss #smolweb #permacomputing #noAI #c #lisp #clisp #scheme #zig #snac
(1)
A riddle: why is Python (the programming language) _natively_ suitable for controlling robots?
(2)
There are other qualities by which Python is at least a spiritual descendant of Lisp.
For example, Lisp is the earliest object-based language and Python is also object-based.
In Python, `==' is to `is' as in Lisp `equal' is to `eq'.
There is a long list of details, such as Python's `import' being similar to Lisp's `require' or `type' being similar to `type-of'.
Type declarations are optional.
Python's doc-strings are syntactically like Lisp's doc-strings.
I very much am interested in looking OS designs beyond #Unix.
For instance I felt a real need for a different programming interface, OS and filesystem while I was doing research. I thought I wanted a #Lisp Machine comeback(hence title of the blog post below). But after research, I found the precise term to be "residential style developement". Below is me blog post:
https://far.chickenkiller.com/computing/do-i-need-a-lisp-machine-comeback/
I have also seen other software developers complaining about storage interface in Operating Systems and programming languages. For instance, here's a quote from Viktor who developers #Marginalia search engine complaining about this:
> This is mostly a post to complain about something > that chafes. I wish there was a programming language (ideally several) that acknowledged that computers have hard drives, not just a processor, RAM and other_devices[].
His blog post is here:
https://www.marginalia.nu/log/53-better-hard-drive-metaphor/
I wonder why genetic programming so often uses a Lisp-inspired paradigm instead of a Forth-inspired one. They are both extremely simple to implement, but Forth has the advantage of being expressible as a linear sequence, so standard genetic algorithm operators can be used on it. If you find Lisp syntax more readable, it would be easy to translate, since they are both inherently nested.
When I say passable: in graduate school I wrote a Prolog interpreter in java (including parsing source code or REPL input), within which I could run the classic examples like append or (very simple) symbolic differentiation/integration. As an undergraduate I wrote a Mathematica program to solve the word recognition problem for context-free formal languages. But I'd need some study time to be able to write these languages again.
I don't know what the hell prompted me to reminisce about programming languages. I hope it doesn't come off as a humblebrag but rather like old guy spinning yarns. I think I've been through so many because I'm never quite happy with any one of them and because I've had a varied career that started when I was pretty young.
I guess I'm also half hoping to find people on here who have similar interests so I'm going to riddle this post with hashtags:
#Coding #SoftwareDevelopment #ProgrammingLanguages #8086Assembly #BASIC #C #Pascal #perl #java #scala #LISP #Scheme #Prolog #Mathematica #ObjectiveC #matlab #octave #R #Python #Fortran #COBOL #Haskell #Clean #Flix #Curry #Factor #Unison #Joy #Idris #Agda #Lean #6502Assembly