Search results for tag #lisp
Apropos of nothing: Big thanks to Shiro Kawai for creating Gauche Scheme, which so far has been one of the best Scheme implementations I have used. It has worked well on every computer I have tried it on so far ({Linux, FreeBSD, MacOS} x {x86_64, i386, aarch64}). It is stable, very fast, and supports a large number of the more recent SRFIs (Scheme language extensions), it has very good compatibility with the R7RS language standard, and the Gauche REPL gosh is pretty easy to use as well.
I always run the REPL in R7RS mode, so gosh -r7 -I. -i . Scheme people, give it a try sometime if you haven’t already!
https://practical-scheme.net/gauche/
#tech #software #Scheme #R7RS #Lisp #SchemeLang #FunctionalProgramming #Gauche
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.
... [SENSITIVE CONTENT]
Why nobody is talking about Jolt, a #Clojure implementation on Chez Scheme?
#lispyGopherClimate #emacs #FSF CONFIRMED @bandali (note the new fediversal #snac account) will join us on the show tomorrow!
Remember it is every Tuesday-night-in-the-Americas being 0UTC Wednesday, or 25 hours from this toot. (Every week since 2022.).
live - https://anonradio.net/
#RSS https://toobnix.org/feeds/videos.xml?accountId=580185 ( @screwtape_channel ). #peertube #lisp
Alt...
The red ink Lispy Gopher Show banner (featuring Maude and not Bandali) unix_surrealism.
anonradio.net
LISPPY
GOPHER
SHOW.
At almost 800 pages The Architecture of Symbolic Computers by Peter Kogge (McGraw-Hill, 1991) is a massive tome on Lisp Machines, logic systems, and other symbolic computer architectures.
https://archive.org/details/architectureofsy0000kogg
#LispMachine #lisp #prolog #FunctionalProgramming #retrocomputing #book
Clasp v3.0.0 released! Congrats to the team :)
https://github.com/clasp-developers/clasp/releases/tag/3.0.0
#lispyGopherClimate #zine ( https://itch.io/jam/zine ) (we are in week -2, where the first issue will be in week 0)
#lisp topic wants that occur to me, (add your own / just submit something completely different).
- square dancing and lisp
- lambdamoo as a lisp cultural artifact
- Making a submission in interlisp medley
- making a(n ANSI CL + clim 2 spec) submission at all, many versions
- lots of loosely lispy art. Basically if it has the lisp to submit it is sufficiently lispy.
- NASA and lisp
It's Sunday morning in Europe! #archive 8UTC Sunday as always #lispyGopherClimate #podcast since 2022.
https://toobnix.org/w/pU6zu95YDdyGKqsxxRf3Vg #peertube live
#RSS (recent times) https://toobnix.org/feeds/videos.xml?accountId=580185
@vnikolov 's Quality Without A Name toot #AI
As much as I can remember about the #lisp community #architecture and Christopher Alexander https://www.dreamsongs.com/Files/PatternsOfSoftware.pdf https://alexandria.common-lisp.dev/
My NicCLIM #IDE demo and the #DL book I am #writing - loose bibliography and sketch of chapters
Alt...
The lisp alien and gopher fighting in the unix_surrealism corpofoss war arc. LISPY GOPHER SHOW
vintage banner recently unearthed.
Reminder to self: the classic 1978 book Anatomy of LISP by John Allen is available online, so add it to the reading list.
https://archive.org/details/mc-graw-hill-john-allen-anatomy-of-lisp
https://archive.org/details/anatomyoflisp0000alle/page/n5/mode/2up
about to commit a #lisp heresy:
car and cdr were obsoleted by destructuring-bind and it's time to say goodbye
where the clhs goes wrong is preventing us from writing (defun teh ((a . b)) (cons b a)) and calling it as (teh (3 . 2)) to get (2 . 3) back, instead we have to write (defmacro teh ((a . b)) (cons ,b ,a))
if they just removed ordinary lambda lists and declared them all to destructure, we could be rid of a 60 year hangover from an ibm architecture
The agonizing slow death of the power user
This is a fascinating article to read. The facts are nailed to the wall in clear and easy to comprehend jargon, even for the non-grey beards
Some quotes
Ask a twenty-two-year-old to connect to a remote server via SSH. Ask them to explain what DNS is at a conceptual level. Ask them to tell you the difference between their router’s public IP and the local IP of their laptop. Ask them to open a terminal and list the contents of a directory. These are not advanced topics. Twenty years ago these were things you learned in the first week of any serious engagement with computers. Today they’re exotic knowledge that even a lot of working software developers don’t have, because you can go a long way in modern development without ever leaving the managed abstractions your platform provides.
And that’s the real damage. It’s not just end users who don’t know this stuff. It’s developers. People who write software for a living who’ve never had to think about what happens between their API call and the response. Who’ve never had to debug something at the network layer. Who’ve never had to read a full stack trace and understand every frame of it. Because the frameworks handle all of that, and the frameworks are good enough, and figuring out how things actually work is optional.
Some facts
Power User
A power user is a user of computers, software and other electronic devices who uses advanced features of computer hardware,[1][2][3] operating systems,[4] programs, or websites[5] which are not used by the average user. A power user might not have extensive technical knowledge of the systems they use[6] but is rather characterized by competence or desire to make the most intensive use of computer programs or systems.
Term use
The term came into use in the 1980s, as advocates for computing developed special skills for working with or customizing existing hardware and software. Power users knew the best ways to perform common tasks and find advanced information before the arrival of the commercial Internet. On PC platforms, power users read magazines like Byte or PC Magazine, and knew enough about operating systems to create and edit batch files, write short programs in BASIC, and adjust system settings. They tended to customize or "supercharge" existing systems, rather than create new software.[7]
Notes
This is systematically done by the factories of technology. I am baffled that a 41 year old litterate person, with secondary school and partial tertiary school, cant tell the difference between an email account, a FB account, a local machine account, a table, notebook and Android phone, from the basic technological perspective. This happened a couple of hours ago, which makes this article very relevant to me.
This person was born two generations ago!
WTF happened to reading manuals!?
I read all manuals I get with hardware I buy, go online to fetch and read, PRINT IF I HAVE TO!
Power Users are a sub-species of homosapiens which is in the greybeard stage.
Eventually we will drop our current corpus and move on to other energy levels of existence
Power users will become extinct in the next generation or two
A bleak future for those left
Z
sources
https://en.wikipedia.org/wiki/Power_User
https://fireborn.mataroa.blog/blog/the-slow-death-of-the-power-user/
#Power #User #Death #Vigil #Eulogy #Abstraction #API #IDE #programming #DNS #networking #File #System #FileSystem #sadness #bleak #future #lisp
Alt...
screencap of site
Alt...
screencap of site
Alt...
screencap of site
Alt...
screencap of site
A compact interpreter for a minimal lisp/scheme dialect. A street lisp.
https://git.sr.ht/~ft/sl
#streetlisp #lisp #unix_surrealism #computers #programming
Alt...
lisp accurate streetlisp alien
The book A Programmer's Guide to COMMON LISP by Deborah Tatar (Digital Press, 1987), along with the errata, is now online with permission from the author.
https://archive.org/details/a-programmers-guide-to-common-lisp
My review of the book:
https://journal.paoloamoroso.com/reading-a-programmers-guide-to-common-lisp
So #ecl project also reached a conclusion what to do with LLM contributions:
https://gitlab.com/embeddable-common-lisp/ecl/-/work_items/826
Long story short: no LLM code in the codebase whatsoever until a legislative consensus is reached (and then we may reevaluate it).
Use “Wind Move Mode.” Enable with this in your init.el file:
(windmove-default-keybindings)This lets you move your cursor from window to window using the shift key with the arrow keys, such that the cursor will move to the window split nearest to cursor in the arrow direction you pressed. This feature has been built-in to Emacs since version 27.1 (the year 2020, which is, for a 50-year-old piece of software, not at all very long ago)
I only learned about this feature a few days ago, and it has instantly improved my quality of (virtual) life. It feels more comfortable and natural than C-x o, and now I use it constantly and without thinking about it. I stumbled upon this feature when creating a new Emacs init.el for an Apple laptop.
I am too lazy to try to keep one single Emacs config for all of my devices. I mean, I could, but unless I am replacing my personal daily driver (where I would copy my entire home directory, including Emacs config), I usually just start a new config every time I get a new computer, especially a work computer. And when I do, I gradually set the configuration variables that I need as I go along, searching the documentation when I can’t remember how to do things.
I’m not the kind of guy who declares “ #EmacsBankruptcy “. I always keep my init.el file simple, only for configuring modes and global variables, and nothing else. I keep my personal macros in other files. So recreating my Emacs init.el for each new computer is one of the few chances I have to stumble across new configuration variables I hadn’t seen before in the documentation.
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