Also CL folks: "I developed an entire #Haskell-like programming language in Common Lisp only to realize its lack of features found in its 50-page standard cousin #Scheme is holding the whole project back"
Richard Gabriel's "Worse Is Better" (1991) is always worth a re-visit.
It's a fairly succinct and technical reflection on why worse design design decisions often win. It also encapsulates why we're all using Unix and Windows running C code rather than more advanced and elegant #Lisp machines.
I'm a wierdo. I don't have a problem with that. And yes, I think that most of us who discover #Lisp and fall deeply in love with it are weirdos.
You only need to look at a fern, or a cloud, or a tree, or a human hand, or water curling in vortices off a rock, to know that God is a wierdo too: the universe is written in recursive functions.
@schmudde@evanwolf "Lisp, face it, is used for advanced research and development in AI and other esoteric areas. It has weird syntax, and almost all other computer languages share a non-Lispy syntax. Syntax, folks, is religion, and Lisp is the wrong one. Lisp is used by weirdos who do weirdo science."
that's extremely dogmatic (literally so), for someone who is attacking someone else for being dogmatic. otherwise i was finding it ok.
@ramin_hal9001@publicvoit yup, same rationale. Shell wasn't too bad, but I was fed up with configuring #Neovim and #tmux. They just never felt... complete. Then it got to the point where my Neovim config kept falling apart because all the plugin updates kept deprecating things, and #Fennel just wasn't lispy enough. For reference - I used #Nix, so adding/removing plugins was a breeze.
It also felt like a lot of Neovim plugins and apps were trying to add to or hack into Neovim what Emacs already did well. #Neovide and #GNvim, #Conjure, Vim Table Mode, #Aniseed and Hotpot.nvim, I could go on. These are all excellent plugins, but Emacs just does them so much better.
#Vimscript was a very simple command language made to do things it never should have. Tmux's scripting language is an even uglier copy, mixed with shell syntax. And scripting in Fennel is somewhat okay until you have to start mixing in Vimscript via strings.
It just all felt... hacky. Puzzle pieces that were never supposed to go together.
#Emacs just feels so much more coherent, or at least #DoomEmacs. Doom gives you the finished puzzle, and detailed, simple instructions on how to rearrange it to make it your own, or even tack on more pieces. It's a wonderful experience. And I just love #Lisp.
「 Now, before you go out and write your next project in Lisp, you should keep something in mind. Lisp is not the fastest or smallest language out there, it was not designed to be so. There are some pretty good implementations of Lisp out in the wild, but don’t expect them to outperform C, Go, Lua, or even Python most of the time 」
via brycevandegrift.xyz
Scheme isn't #lisp, insofar as lisp means "weighed down by the traditions of dead generations like a nightmare on the brains of the living." We have pattern matching that rivals statically typed languages. Fight me.
Why in #SICP the word "procedure" are used instead of "function"
It's seems a bit confusing. As I remember, term procedure is about just an action, some effect, without returning a value (aka void function). #LISP always returning the value, ok, but... why do not use the word "function"...
Otherwise why do not use word "procedure" if there's no procedures in (probably only my) classical definition
Medley Interlisp has the most tightly integrated combination of system software, application platform, programming language, development environment, tools, and runtime platform I've ever experienced.
A rare "whole greater than the sum of its parts" level of synergy mostly seen only on Smalltalk workstations and Lisp Machines.
#Lisp(s) are the only programming environments that enable a prototype-to-production development cycle for non-trivial projects in a way that is predictable.
I think something the scheme community could learn from Haskell is to lean-in on it's prestige. I see so many people post about how they were never able to figure out how to use scheme in any practical way, and most schemers I've spoke to said it took them about a year to get really compfortable. But I think the #scheme community has traditionally advertised it as "so easy, you can learn it in an afternoon!", and so people, often times already coming from some other #lisp like #clojure, expect to be able to just pick it up, and when they fail to they think the language is lacking. But nobody comes to #Haskell with such expectations, and the Haskell community never advertised it as super easy and quick to learn. In my experience, Haskell has always been sold as "takes time to learn, but is worth it".
#lisp y #gopher show w/ screwtape as named by gef in about 4.75 hours #music original electric by noted kiwi https://cyanmentality.bandcamp.com/
Clarifying my thoughts on why current generative AI are bad #gopher examples of my bunny hopfield nets with memory collisions, but higher polynomial update functions spacing the memories out removing the collisions. Pictures and ASCII. STILL WIP. #lisp discussion of the great commentary I got on my failure to TDD, a bit on interlisp and git.