Old paper:
John Launchbury and Simon L Peyton Jones. 1995. *State in Haskell*
https://sci-hub.st/10.1007/BF01018827

What interests me more is that the journal used to called *LISP and Symbolic Computation*, the intersection of the two topics that I am most interested.

Later the the “LISP” in the journal name was changed to “Higher-Order” in 1998, after which the famous #R5RS
was published on it.

#Haskell #LISP #Scheme #SymbolicComputation

lisp - How is Racket different from Scheme? - Stack Overflow

" #Racket is ultimately based on #R5RS, and not R6RS and not a strict superset of either. I don't think it can be called 'Scheme' because it's not backwards compatible with any Scheme standard."
https://stackoverflow.com/questions/3345397/how-is-racket-different-from-scheme#:~:text=Racket%20is%20ultimately%20based%20on%20R5RS%2C%20and%20not%20R6RS%20and%20not%20a%20strict%20superset%20of%20either.%20I%20don%27t%20think%20it%20can%20be%20called%20%27Scheme%27%20because%20it%27s%20not%20backwards%20compatible%20with%20any%20Scheme%20standard.

@robinheghan I started using Guile #Scheme because it was the extension language for the gEDA electronic design suite.

The Guile manual + #R5RS were all I needed for teaching myself — the project I was working on had plenty of problems at different levels of difficulty.

#r5rs is dying and #r7rs-large cannot be born; now is the time of #clojure(s)

#scheme #lisp

Hot take: in terms of the language specified treated independently of the social process of standardization itself, everyone's beloved #r5rs is actually the worst post-#r4rs scheme, and #r6rs is easily the best and most revolutionary, hence the controversy surrounding it.

#lisp #srfi

@ramin_hal9001 the thing is, I would say this is starting to change with r6 and #r7rs implementations, and #akku does a pretty job of working out the compatibility between different implementations (but the guix package needs some fixing... on my TODOs).

but I agree about the pressure to pick the right one, it drove me mad, but I also think that the idea that getting used to multiple schemes is impossible, and it should even be encouraged to work with a few of them, because once you've navigated a couple, they're all kind of the same at root. but I think people should stick to one for their first year.

it's primarily just the #r5rs implementations that differ wildly. I think theres this mythology that r5rs was this legendary, impeccable standard, and that the process went astray after that, but the truth is that #r6rs really was a massive improvement, and r7rs-large will be something like r6rs (creating an r7rs compatability later for r6rs schemes is a matter of defining a module and a few identifier-syntax macros). problems with post-r5rs are primarily social, rather than technical imo.

You know #TDD ?! What? I mean #tootDrivenDevelopment ? 🤔🤔

♥️ I need help to figure out what it looks like! ♥️

I start with a simple #scheme #code #snippet and you modify it. The resulting code has to fit in one toot!
If you can't execute the code. It's broken. The last committer should fix it.
So make it portable ! 🚀

(display "hello schemers")

#scheme #schemer #schemers #lisp #lisper
#r5rs #r6rs #r7rs #coding #programming #fun #friday #guile #chezscheme #gauche #racket #chickenscheme #gambit