7 ms·
R7RS versus R6RS (2018)
- jimbob45 7y agoI was struggling to find a concise summary of the debate between R7RS vs R6RS earlier this year. This article was the best I found to that end.
- slim 7y agolast year
- haolez 7y agoI thought that the whole point of Scheme is for it to be easy to implement. R7RS seems more aligned with Scheme's vision.
- bitwize 7y agoEase of implementation leads to a maze of twisty little implementations, all different. It also leads to unaccounted-for corner cases (see: why C is deprecated). The major implementations, Guile and Racket, both embraced R6RS.
- buzzkillington 7y agoGuile has not embraced R6RS: > R6RS significantly expands the core Scheme language, and standardisesmany non-core functions that implementations—including Guile—have previously done indifferent ways. Guile has been updated to incorporate some of the features of R6RS, and toadjust some existing features to conform to the R6RS specification, but it is by no meansa complete R6RS implementation. SeeSection 7.6 https://www.gnu.org/software/guile/manual/guile.pdf https://www.gnu.org/software/guile/manual/guile.pdf Neither has Racket, they aren't even calling themselves a scheme any more.
- pmoriarty 7y agoNeither does Chicken Scheme https://www.reddit.com/r/programming/comments/1s9rg/lead_developer_of_chicken_scheme_speaks_out/ https://www.reddit.com/r/programming/comments/1s9rg/lead_dev...
- akkartik 7y agoAre there any complete implementations of R6RS?
- widdershins 7y agoI think Chez is pretty much compliant.
- abjKT26nO8 7y agoChez Scheme.
- bitwize 7y agoRacket also has a #!lang r6rs.
- bjoli 7y agoThe upcoming 3.0 release has an r6rs mode that makes r6rs easier to use. The r6rs incompatibilities are, apart from (rnrs io ports) and the condition system rather small. The incompatibilities can be found here: https://www.gnu.org/software/guile/docs/master/guile.html/R6RS-Incompatibilities.html#R6RS-Incompatibilities https://www.gnu.org/software/guile/docs/master/guile.html/R6...
- Avshalom 7y agoI mean originally it was just an exploratory language, something small enough that Steele and crew could keep it all in their head but with lisp flexibility so they didn't have to re-write it everytime they thought up something new. As far as I know it was never meant to be like a tool to teach compiler/interpreter writing or anything. That said a big part of R6 which is mentioned in article is that code was not very portable between R5s (N.B. it wasn't much more portable between R6s) and in some sense if your implementation can't run anyone else's code, what have you actually implemented? Something that looks like scheme is easy implement to be sure but I think R6 was trying to make it so that 'scheme' was a language and not an aesthetic.
- bitwize 7y agoR6RS is like systemd: a couple of lone motherfuckers, disappointed in the glaring inadequacy of the status quo which the techie establishment refuses to see, go off and develop a comprehensive system. It's accepted by most of the user community and the major implementations/distros. But the techies, having been sidelined, scream "no!", stubbornly dig their heels in against the inexorable tug of progress, and spend the next fixnum years bikeshedding the details of what their retrogressive Scheme should look like. I use "techies" here in the disparaging, Ted Nelson sense. I see you. Because I used to be one of you. But now I'm with Eli Barzilay: y'all should have just shut your mouths, sucked it up, and accepted R6RS because it was leagues better than any proposed alternative. And all this whining is pretty much for naught because Scheme is an irrelevant language in 2020 anyways. R8RS is already in wide use -- it's called JavaScript.
- vsskanth 7y agoWait, what really ? JavaScript evolved from scheme ?
- bitwize 7y agoBrendan Eich was originally going to embed Scheme into Netscape. But higher-ups said no, it has to be familiar and resemble popular languages like Java to get any traction. (They were right.) So Eich went in and threw something together over a few days, and boom -- JavaScript. JavaScript isn't Scheme, but it's close enough for most programmers working in the real world. (There's even a JavaScript version of SICP.) And while Hackernews rubs one out to Lisp Machine porn, our computers are slowly turning into JavaScript Machines.
- krackers 7y agoAre there any other features in common other than closures and first class functions? I'm not sure that makes Javascript closer to Scheme than any other language like Python (which also has a version of SICP).
- 7y ago
- apocalypstyx 7y agoStands off to the side waving R4RS flag.
- pmarin 7y agoI can't not explain why but I always have found the document more easy to read and the hygiene macros steal all the fun from lisp.
- nils-m-holm 7y agoYou are not alone! S9fES is still R4RS. :) https://www.t3x.org/s9fes/index.html https://www.t3x.org/s9fes/index.html
- jgon 7y agoI think this is a really fair summary of the technical differences between the two standards written from the perspective of a person who favors R6RS. I especially agree with the point regarding error signalling and the lack of effective facilities for that in R7RS. I should also say that my perspective is that of an outsider, a user, not someone who is involved in implementing scheme, or in the standards process. With that said, I feel like this post does not capture the social context of R7RS vs R6RS and without that you can't really understand the overall picture. Scheme has been around for decades and there are probably dozens of implementations. Almost every one of them supported R5RS. Unfortunately this standard didn't specify enough to allow for easy interoperability of scheme programs between implementations, depending on what you were trying to do. So everyone ended up just picking their own scheme and running with it. R6RS tried to offer enough of a standard to allow for interoperability between implementations, particularly in offering a module/library syntax, and a bunch of the other things listed in the post. The main problem, and really the one that triggered R7RS, was that it was a large enough standard and required enough work that not many implementations updated to conform to it. The standard was ratified in 2007 and when I was looking around for conformant implementations I didn't find a lot. There was Ypsilon scheme, which has since become abandonware. Ikarus scheme by Abulaziz Ghoulum was super fast but was also abandoned. Larceny scheme was compliant I believe but I didn't use it much. Kawa scheme worked to get there but was still not conformant by 2012. Guile never fully implemented it. PLT Scheme implemented it, but 2 years after was already making announcements about leaving Scheme behind and became Racket in 2010. MIT Scheme of SICP fame basically said they'd never implement it. The crown jewel was probably Chez Scheme, still to this day one of the best language implementations period. But it was proprietary in 2007 and cost money. You could use the interpreter based implementation Petite Chez Scheme, but it still had other restrictions I believe. Committing to R6RS as the standard going forward meant abandoning most of the existent implementations, and thus most of the body of code people had written for them. In trying to unify the Scheme world going forward, R6RS was potentially asking for a large schism. Please note that the previous sentence isn't a value judgement. Maybe Scheme would be in a better place given the technical merits of R6RS. I can't deny that. But that is how the world looked (in my view) when R6RS was the scheme standard of the day. In comparison after R7RS was ratified, many implementations worked to be conformant. Guile is close, Kawa is conformant, Gauche Scheme implements R7RS, Ypsilon is another, Chibi Scheme, Larceny, etc, etc. In terms of standards adoption there's no contest. Writing this post from 2020, where Chez Scheme is open sourced and free, Akku scheme is a great implementation of R6RS, and we are starting to get package repos for Scheme, maybe R6RS would have been the better choice. Maybe all those other implementations should have fallen by the wayside and we'd all use Chez Scheme, much like CPython is the canonical Python (except Chez Scheme is incredibly well implemented). But at the time the decision was made to make a new standard, a very explicit decision was made to abandon the "easy for users, hard for implementers" motto of R6RS, because what is a language standard without implementations? My hope is that ongoing work can build on R7RS and get us to the level of excellence and ability to build things that R6RS gave, and maybe we can end up having our cake and eating it to.
- jhoechtl 7y agoI seldom saw such an incredibly weak argumentation as in section "The number argument". Yes, If someone wants Scheme to remain an academic toy language, this might make sense. I followed the discussion and schisma which resulted in Racket for good. If you want to have a sane language, some pages of specification and rationalization are required, as has been done for R6RS. If the professors fear that students will no longer be able to implement their Scheme interpreter in a term because the spec has become to complicated please call the language somehow different and stop to encumber the development of an otherwise great language!
- QuesnayJr 7y agoThere is definitely a split between the people who think it's interesting to program in Scheme and the people who think it's interesting to program <i>a</i> Scheme (particularly to do so in Scheme itself). For the second group, the Scheme language is more of an aesthetic object than a programming language. The length argument is also a stand-in for the argument about Common Lisp versus Scheme. CL is pretty carefully defined, so the CL spec is pretty long, and some Schemers used this as an argument against CL (that it was bloated). Now suddenly the Scheme spec was also long, so that argument was gone.
- eadmund 7y agoIt really all depends on what one wants. If one wants an excellent academic exercise, Scheme is pretty great. If one wants an excellent industrial language, Common Lisp is right there. I am sympathetic to R6RS because it tries to make Scheme more useful for real programming — but in that case why not just use Common Lisp, which is even more useful for that purpose?
- codeflo 7y agoI’m not convinced CL is more useful for real world usage. People sometimes fall into the trap of thinking that more features are always better. With programming languages, that’s rarely true, because even features you don’t use cost you something — in terms of training new programmers, and every time your dealing with other people’s code. (And note here that in real-world projects, most of the code you have to modify and debug isn’t yours!) Of course it’s possible to go too far the other way, and R5RS leaves too many questions unanswered. But in my opinion, simplicity is also an important feature, not just academically, but in practice.
- atsmyles 7y agoWith all due respect to the author, I followed the r7rs standardization closely, and disagree with his bottom lines. 1. On the number argument: Even the author acknoweldges that R6RS is twice as large. Regardless of the fact that the standard library is the other half, the fact is that the standard library is a requirement for R6RS. Because of the controversies about it (the condition system, record system, hash table library), the R7RS standard was purposely split into 2 parts, the R7RS-small and the R7RS-large. The R7RS-large standardization is an ongoing project. 2. On the condition system: The fact is that horse already left the barn. Most major implementations already had their own condition hierarchies. The only way to reconcile their existing conditions would be to have a translation layer which would be inefficent. Conforming to R6RS condition system would mean throwing out most of the code that people who use those implementations depend on. R7RS focused on providing a basic error system with a purely procedural interface, which combined with cond-expand and the library system, can allow people to write portable code. So the idea that the standard committee doesn't believe "Safety is not a desirable language feature" is unwarrented. 3. On Optional is better argument: Sure you can have an R6RS with restrictions, but then it isn't R6RS, it is a R6RS-like scheme. Using feature identifiers is at least a better way to create portable code. If you have a library that requires unicode, you can specify that in the code. 4. On syntax-case, one of the costs of having it is a more complicated library system, with import and export levels. Read it yourself, http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-10.html#node_sec_7.2 http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-10.html#node_se... . R7RS-small decided to be more conservative in this area. Overall, I think that the way that R7RS standardization has worked to evolve the standard was the right approach. They focused on the most important needs for scheme ( The library system, a basic record system, basic error handling) while avoiding adding features that were overly controversial.