10 ms·
WTF is going on with R7RS Large?
- mellosouls 3y agoDiscussion from yesterday: https://news.ycombinator.com/item?id=37164243 https://news.ycombinator.com/item?id=37164243
- veave 3y ago>Scheme may be a small island, but when it has an earthquake, it makes waves through the whole archipelago of programming languages. It's more like people are addicted to drama. Following something like this when you don't use Scheme is like watching reality TV. It's human nature.
- GhostWhisperer 3y agothis, if you had not know what r7rs was untill a few days agor, or still don't, hit 'hide'
- worldsayshi 3y ago> people are addicted to drama Is this an currently escalating tendency or has it always been like this? I mean the human nature has always been there but is our current social media landscape amplifying it to 11?
- rgoulter 3y agoSomewhat related, I think, is the argument about 'victimhood culture'. https://en.wikipedia.org/wiki/The_Rise_of_Victimhood_Culture https://en.wikipedia.org/wiki/The_Rise_of_Victimhood_Culture (The Wikipedia article doesn't cite any criticism, unfortunately). Roughly, it argues that society has progressed from "up to victim to restore their own honour" to "society restores dignity to all". And then 'victimhood culture' would be an over-correction where people seek to be victims. I could believe that society has changed the way it approaches conflict. But, I'd think social media stuff changes the shape of traffic/attention. I would think people are not inclined to be curious to hear both sides of some conflict.
- stonetrw 3y agoThe issue here is that the current generation of programmers seem to want political power more than doing actual work. Everyone and their grandmother saw the huge decline in quality between r5rs and r7rs. The people who wanted to do stuff created racket. The people who want to rule a graveyard stuck with the rnrs process. Seeing this happen to scheme whose whole purpose is the ability to create languages is bizarre. I can understand a fight like this over gcc or Linux,a fork there isn't something a single person can do as a weekend job. Scheme on the other had is absolutely something a single dev can design and implement in a few months worth of weekends.
- version_five 3y ago[flagged]
- deleted 3y ago[deleted]
- Havoc 3y agoIt’s really starting to look like language design goes better via benevolent dictator. Committees don’t lend themselves to coherent and consistent overall vision
- rcarmo 3y agoI'm starting to think that just doing a set of "stdlib" packages for R6RS that roughly matches what Python has (including essentials like SQLite, HTTP servers and requests and JSON/EDN support, together with some common patterns) would have been easier and actually gotten somewhere by now :)
- varjag 3y agoCommon Lisp committee did just fine: produced one massive standard which has been a lasting foundation for three decades since, and dissolved. Certain popular non-Lispy languages have standards committees too with generally positive effects.
- bmacho 3y agoHaskell committee did a fine job as well > After the release of Miranda by Research Software Ltd. in 1985, interest in lazy functional languages grew. By 1987, more than a dozen non-strict, purely functional programming languages existed. Miranda was the most widely used, but it was proprietary software. At the conference on Functional Programming Languages and Computer Architecture (FPCA '87) in Portland, Oregon, there was a strong consensus that a committee be formed to define an open standard for such languages. The committee's purpose was to consolidate existing functional languages into a common one to serve as a basis for future research in functional-language design. [...] https://en.wikipedia.org/wiki/Haskell#History https://en.wikipedia.org/wiki/Haskell#History
- crote 3y agoI don't think Haskell is a good example. In my experience, real-world Haskell requires enabling half a dozen language extensions, most of which have only been implemented for GHC and some of which are mutually incompatible. Over the years Haskell has evolved from a well-defined language into "anything people managed to get merged into Haskell". Learning it is now an absolute nightmare as you are basically required to understand a dozen poorly-documented extensions to use even very basic libraries.
- cb321 3y agoThere was amusing humor in this writing with allusion to Douglas Adams & Kurt Vonnegut (& maybe others I missed). This seems especially apt for a young person with ambitions to chair a committee for standardizing such an old language.
- rcarmo 3y agooh yes. Worth reading for those alone.
- mijoharas 3y agoI noticed the Douglas Adams reference[0] but couldn't remember where it was from, so thank you! What was the Kurt Vonnegut reference? [0] In the beginning, Scheme was created. This made a lot of people very happy and has widely been regarded as an excellent idea.
- cb321 3y ago"So it goes" was a line used gajillions of times by Vonnegut in a similar way.[1] So, at least that. [1] https://www.goodreads.com/quotes/660696-so-it-goes-unlike-many-of-these-quotes-the-repeated https://www.goodreads.com/quotes/660696-so-it-goes-unlike-ma...
- thaumasiotes 3y ago"So it goes" can't be called a Vonnegut reference unless it's surrounded by other Vonnegut references, because it's a perfectly ordinary phrase in common use outside Vonnegut. Think of it this way: "So long, and thanks for all the fish" is a Douglas Adams reference, but mentioning a dolphin isn't.
- cb321 3y agoAn "allusion" is an indirect reference/pun. The degree of indirection is clearly subjective. The phrasing great grandparent recognized from Adams (at least one other person) is actually a negation of the famous line from Restaurant At The End of the universe. (EDIT: which, for the record, is "The story so far: In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move.") I do agree "So it goes" is more of a stretch here especially since dpk seems to live in Germany and it's a common translation of "So geht's" which may be more common in Germany than "So it goes" in primarily English speaking countries. I.e., how "perfectly ordinary" may be reader-dependent. I think it's a stretch supported by the Adams adaptation two paragraphs earlier, though. In primarily English speaking countries it is "signature enough" that they use it for the Vonnegut Library: https://www.vonnegutlibrary.org/so-it-goes/ https://www.vonnegutlibrary.org/so-it-goes/ , but sure it comes up a lot more than "thanks for all the fish". I think these are disputes of degree more than kind. TL;DR - I stand by my guess, but you'd have to ask dpk to be sure. EDIT: and Vonnegut's parents were German - so, this may also just be V being an "ambassador" making the more "perfectly ordinary" in one domain more "signature" in another domain. It happens.
- thebruce87m 3y agoI thought this was about issues with an EC2 instance
- deleted 3y ago[deleted]
- adrian_b 3y agoWhile some of the things said there cannot be assessed by an outsider, the last paragraph that starts with: "Scheme has an outsized importance in the world of programming languages compared to its actual use in industry, because it has so often pioneered features that later broke into the mainstream.". is doubtless true. Scheme belongs to a list of at least two dozen historical programming languages that have introduced very important innovations and anyone who has the ambition of creating or improving any programming language should be familiar with all of them. I consider sad the fact that all more recent attempts of introducing new programming languages appear to have been made by people who happened to have some brilliant idea about how to improve some feature of programming languages, but otherwise they seem to have little knowledge about past programming languages, so they combine their new good feature with various bad features from a few languages that happen to be popular now, due to various historic accidents, even if already many decades ago better alternatives were known. Because of this continuous reinventing of the wheel, all the available programming languages include various combinations of good features with bad features, so none is completely satisfactory.
- acegopher 3y agoDoes there exist a catalog of these pioneering or best practice features, and bad features that should not be replicated? It might be worthwhile to have a tome of such for future language designers to learn from.
- winter_blue 3y ago> Does there exist a catalog of these pioneering or best practice features, and bad features that should not be replicated? It might be worthwhile to have a tome of such for future language designers to learn from. A "programming language features" wiki cataloging such features (and their pros/cons) would be amazing.
- adrian_b 3y agoI am not aware of any such catalog, so I had to compile one for my personal use from reading a very large number of old documents. There are a few books about the history of programming languages, but they are mostly descriptive and contain little comparative analysis of the value of various features. Moreover because due to space limitations they have to mention only a part of the features of the languages that are described, the choice of what to mention and what to ignore in the description of a language may be not the most appropriate from the POV of an experienced programmer. Therefore I have found more useful the original manuals of various programming languages, from when they have been launched, during the fifties, sixties and seventies of the 20th century. After 1980 the pace of innovations has slowed a lot and most of the languages that introduced those innovations are still used today, so finding documentation about them is no longer difficult. While C was itself an innovative language, the fact that it included very few of the features of the languages contemporaneous with it ensured that many of those features are not available even today in mainstream languages, while other features have become widely used only after decades after their invention, for instance iterators have already been introduced in 1974, in the same year with C, but they have been revived only a quarter of a century later. Fortunately now there are a handful of Internet sites dedicated to the preservation of the history of computers and programming languages, from where it is easy to download most of the old documentation.
- bunabhucan 3y agoSomeone should create a steering committee tasked with forming a working group to explore a formal standard describing the process of open source project bifurcation and stagnation.
- rcarmo 3y agoThat someone would likely suggest that the venue for that committee's first meeting would be a reclusive island somewhere in the Pacific with an unlimited supply of pina coladas.
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]
- samsquire 3y agoI have no context but I'm going to tell you what I think anyway. I think this is Conways law in action: See W3C, Whatwg and C++ standards committees. The work of specification difficult and the work is complicated and hard. I've never written a standard but I imagine it's very difficult. I've thought how we can use Conway's law directly to engineer technical and social systems that are robust and meet people's needs. One of my ideas is that for a group of different individuals and differing interests and priorities to collaborate, you need to recursively define collaborations and treat them as portfolios where the traversal of those collaborations/interactions is a standard, like Git. What do I mean? I want X, so I announce I'm doing X and how I'm going to do it and I do X. Then I publish X. Then someone says I want that, can I import it. X isn't to their tastes, so they announce they're going to change it to do Y. Or they negotiate with the author of X to change it to do Y. This is a collaboration between those two entities, it's a portfolio of collaborations. That's a standard right there. The doing X is the important part. In other words, the collaboration between parties is reified communication and agreement that is actually imported and used. Otherwise you get this https://xkcd.com/927/ https://xkcd.com/927/ Attempting to do the thing and doing the thing (implementation) are inseparable from standard work I think.
- piva00 3y agoIn my mind the complication in this is: given you did X, and is using X to do A, when Y is proposed and is not compatible with how X works to do A then you have the cost of migration/adaptation of whatever is using X to converge to Y while still being able to do A, otherwise you end up in the same issue with competing standards. This can be much, much worse if it involves anything that is not purely software, you can't adapt older hardware using a standard (let's call it notUSB) to iterate over an improved notUSB-with-appendages, and if notUSB-with-appendages required modifications incompatible with notUSB you just created 2 standards that don't solve a general problem. Standards is something that a lot of people have thought about over centuries, any improvement on the process has probably already been considered by many smart folks so I don't think there's a simple coordination solution to it.
- samsquire 3y ago
- codeflo 3y agoIt's possibly an unpopular take, but it's not completely clear to me what community-driven programming languages gain from a standards process anyway. (At least if the intention is to really standardize the complete thing, bells and whistles included, not just some tiny core, as R5RS did.) If you have multiple adversarial commercial implementers for something, a standard makes perfect sense. It's still a lot of work, but necessary because otherwise, you wouldn't get things to interoperate at all. That's true for things like HTTP, or Bluetooth, or JavaScript, or C++. But for a community project, having one blessed implementation and iterating quickly has proven to be the most successful model, in my opinion. I can point towards Python, Rust, even PHP for examples. Even Haskell, which started out with a written specification, has at this point de facto been forked into the much richer language called "whatever GHC understands".
- deleted 3y ago[deleted]
- _ph_ 3y agoScheme isn't "a community project". It is an universe of many implementations. Having an agreed standard for this is very valuable. It gives a reference, which everyone will want to follow for interoperability. But by creating the standard, things are discussed, so flaws might be discovered and avoided and of course, it gives a clear definition.
- xedrac 3y agoIn practice, Scheme isn't interoperable - you pick a Scheme implementation and pretty much stick with it. Different schemes implement different subsets of SFRIs, and many bring their own non-standard batteries to the table. I think having r7rs large would eventually make the language more interoperable.
- rollcat 3y ago> But for a community project, having one blessed implementation and iterating quickly has proven to be the most successful model, in my opinion. That's not how Scheme works, and I think it's important for both Scheme and PL research/design groups in general that they move the way they do. Each Scheme implementation is in fact its own language, with its own goals, focus, community, etc. E.g. Racket has very different goals (like PL research, education) from Stalin (aggressive optimization), Guile (ease of embedding), or Chicken ("real world" usage). Both the RnRS and SRFI processes are more like guidelines for the implementations to follow, to enable at least some of the code (usually libraries) to be portable. When you're writing your Scheme program, you're usually not targeting "R7RS" or "R5RS + SRFI-1" or whatnot; you're writing and running your program using Chicken, it's a Chicken program much more often than it is a R5RS program. If you later decide to port it to Racket, you will usually have much less porting work to do, but you'll still need to figure out how to do many of the mundane things omitted by the standard, like OS threads or FFI. It's much more useful to think of Scheme as a loosely-tied family of languages, pretty much the same way you can think of UNIX-like OS's. Your average UNIX will surely give you a /bin/sh and a printf and a malloc, but the really interesting stuff (like kqueue, io_uring, DTrace, etc) is why you choose to stick with one over the other, and what motivates different groups to experiment / innovate / contribute.
- twic 3y ago> To move beyond R5RS, a Steering Committee was formed in 2004 which appointed editors to specify an R6RS. [...] A new Steering Committee was elected by those interested in Scheme in 2009 > All of the members of the Steering Committee have become somewhat less active in the Scheme community in recent years. Though we’ve seen occasional input from individual members, the Steering Committee as a body hasn’t taken any action since 2013 when the small language report was ratified. When the changes made in 2022 were being discussed, we got no guidance from the Committee at all. In short, we’re not sure the Steering Committee exists as a single, functioning entity any more. How significant is this? Is there an actual process for forming a steering committee? From where does it derive its authority? If the current one is defunct, can they just form yet another one?
- deleted 3y ago[deleted]
- BaculumMeumEst 3y agoWhat advantages would a finalized R7RS large have over Racket, aside from enabling interoperability between implementations?
- butterisgood 3y agoWhat advantage does any standardization have aside from interoperability?
- bjoli 3y agoWell, first of all Racket more closely resembles r6rs. The main large r6rs implementations (guile and chez) both have proper threads (guile even has a parallel CML, which is probably my favourite way to do parallelism of all time) and a startup time measured in single digits (ms) compared to hundreds for racket and something like 80 for racket/base on my slow computer.
- BaculumMeumEst 3y agothank you for the reply. i've been meaning to check out both guile's concurrency features (i had only heard of fibers) and gerbil's actor stuff
- twic 3y ago> At the same time, the community identified that there were two groups with slightly different concerns about what R7RS Large would look like: some were concerned that the small language itself didn’t impose strict enough semantics for a safe high-level programming language,§ > § Indeed, the small language doesn’t even enforce bounds checking, even though almost all implementations do it. Such are the sacrifices for a language which might be expected to work on a tiny microcontroller. ↑ Okay but nobody in their right mind is writing Scheme for microcontrollers. I don't mean that nobody is doing that, but that the people who are are fringe weirdos whose desires should not be allowed to disrupt the evolution of the language for the rest of its users!
- kylec 3y agoPlus, if you want to use Scheme on a microcontroller, wouldn't it be better to use R7RS Small anyway?
- NikkiA 3y agoThat's the point, it's referring design decisions R7RS-small made, as being due to the possibility of running it on microcontrollers.
- neilv 3y agoFor production purposes, I would normally try not to run GC on a traditional microcontroller, whether it's Scheme, Python, JVM, or anything else. But it's maybe worth noting that using Scheme metalanguage abilities to generate non-GC target code for a microcontroller could be very sensible. For example, you have nontrivial control behavior, and there's a short lead time on the controller or device. So, you could define a macro/minilanguage to support modeling the behavior in terms of Harel Statecharts, and initially (for very quick development) have that expand to executable normal Scheme code, for development/testing/simulation. Then, once you've gotten the behavior you want, you tweak the macro/minilanguage a little, to also expand to non-GC target assembly, for the microcontroller dev board or device that you ordered when you started. (Racket syntax extension and submodules are especially nice for doing something like this, but you can also do it with more basic Scheme.)
- sigzero 3y agoWhat a really great write up on the situation (from a certain point of view). Nice. I still want to play with either Chicken Scheme or Racket some day.
- bigfishrunning 3y agoI love chicken scheme; I try to sneak it into software I'm writing often. It usually elicits eyerolls from my peers, but I have my fun...
- mrweasel 3y agoDo you sneak it in as the language for the implementation or as a DSL or scripting language? It's an interesting little language implementation, which I enjoy playing around with, but I never found any project where the team as a whole wasn't better of with something like Python.
- FrustratedMonky 3y ago>"The number of people who could credibly become the new chair is limited; the number of people who want it even fewer." I've noticed this trend in a lot of technology fields of late. I hear a ton about tech layoffs, and yet highly competent people still seem rare.
- _ph_ 3y agoHighly compentent people are rare. And those usually are very busy, especially if at the same time there are layoffs. And if you are compentent and have a plate full of exciting things to do in front of you, it is difficult to find the time for such a committee job, however important that on the long term might be.
- dragonwriter 3y agoHighly competent people may or may not be rare depending on exactly where you divide the line, but competent people in tech that are also competent to this kind of community wrangling are definitely rare, and people sharing both those competencies, with the tech competency in the right domain, who are interested in a particular community-wrangling job, and who can be trusted in it (which is distinct from either kind of competence) are often extremely rare.
- mark_l_watson 3y agoI am an outsider in this conversation (in the last 40 years 95% of my Lisp work used Common Lisp, 5% some Scheme dialect). I do have a recent frustration experience that is relevant though: last year I was thinking of making a serious effort to use Chez Scheme more and I hit a minor roadblock trying to find a library to UUENCODE text. Maybe I was just having a bad morning, but it was frustrating. The Racket language had a ready to use library but I really wanted to use Chez.
- spdegabrielle 3y agoJust use Racket! (Racket uses the Chez compiler)
- mark_l_watson 3y agoI often do. I actually like the IDE, sometimes using it instead of Emacs with the Racket support.
- gorjusborg 3y agoThis interaction illustrates my thought on the wisdom of supporting two language 'profiles'. It seems like the 'small' profile matches what I expect from Scheme's brand: useful minimalism. The 'large' profile seems off-brand. I get why it would be useful to have a Python-like experience (where 80% of problems can be solved with the stdlib), but doesn't that describe Racket? I'm not suggesting that a batteries included standard Scheme would be a bad thing. It's just that it pretty much already exists (Racket started as a Scheme).
- _ph_ 3y agoLacking libraries can be quite a source of frustration, but would it have been so difficult to implement that functionality? In my experience, looking for a library and making it work often takes more time than to implement it.
- mark_l_watson 3y agoThat is a fair point.
- Y_Y 3y ago> I hope we could at least find some source of authority to give some kind of future specification its seal of approval. > The situation reminds me somewhat of the First Council of the Vatican, which was suspended in 1870 after the unifiers of Italy invaded Rome, but was still technically in session until it was formally closed in 1960 in preparation for a new, Second Council of the Vatican. Though the (presumably Protestant) author is understandably reluctant to come out and say it directly, it is clear that she knows that the ultimate guidance on Scheme language spec comes from its primary industrial user, the God of Abraham[0]. As such it's only natural the authority for approving R^(+ n 1)RS be vested in the Holy See with the pontificate responsible for the procedural and spiritual aspects. [0] cf. that one old xkcd strip
- cameron_b 3y agoAhh the footnote on the forecasting based on the first and second Vatican Counsels forces me to offer additionally as a corollary the drafting of the Westminster Confession of Faith [0] It was commissioned by the Parliament of England to settle theological disagreements between the Church of England and the Church of Scotland ( the progenitors of the Anglican and Presbyterian denominations respectively ) which were a major component of the English Civil War. super short version - the Presbyterians wrote most of what came of the documents and ratified it completely, the Church of England red-lined it heavily and they never adopted it in full. [0] https://en.wikipedia.org/wiki/Westminster_Confession_of_Faith https://en.wikipedia.org/wiki/Westminster_Confession_of_Fait...
- ducktective 3y agoI have an idea for maintaining backwards compatibility in programming languages. Why not support old features of the language in the new version of the compiler/interpreter? This seems to be particularly feasible in Lisp/Scheme family of languages due to the fact that ASTs are edited directly in source code. For example, each library declares its target version of the compiler, then newer compiler first translates the library to new syntax, then integrates it with other dependencies. What's wrong with this line of thought?
- neilv 3y agoGood thought. Racket does this and more, for a long time. For the "more": you can do it not only for other dialects of the same language, but also for very different languages. And often to make them interoperable between languages. (For one simple example, long ago I made a fairly simple `#lang sicp` that translates the old dialect of MIT Scheme used by the SICP book, to Racket, using some simple syntax transformation and the module system.)
- grapehut 3y agoIt's often not that simple. As a concrete example, I think Golang made a giant mistake with 'nil interfaces' ( e.g. https://go.dev/tour/methods/12 https://go.dev/tour/methods/12 ) which can lead to extremely confusing and weird code ( e.g. https://go.dev/play/p/Qk1g9tSwQcw https://go.dev/play/p/Qk1g9tSwQcw ). So let's assume there was wide spread consensus that it's a terrible idea and it should work like every other programming language. There is really no obvious way to simply "convert to the new syntax"? And trying to have "go with nil interfaces" library interact with "go with normal type system" would be it's own can of worms. Like in this case, the only realistic path I could see would be you deprecate it, then you start warning, and then in like 10 years or something you fully remove it?
- layer8 3y agoIt still breaks compatibility for the library maintainers, and the results of automatic translation often aren’t pretty (as a basis for further development). It’s also difficult to test or prove that the automatic translation is 100% correct on arbitrary code. Furthermore, as a sibling comment notes, some language changes are made virtually impossible, even with source code translation, if backwards compatibility needs to be maintained. Sometimes there is really no substitute for getting things right from the start.
- contravariant 3y ago> An informal group evolved the language through revisions known as RnRS (a mathematical pun with a reference to Algol hidden in it), In case anyone else is wondering what the pun was in the name R^nRS. I didn't manage to find anything on google (may have used the wrong keywords), but GPT powered phind.com does manage to find an answer: > The pun in RnRS, in reference to Algol, is a play on words involving the names of the two programming languages, Scheme and Algol. RnRS stands for "Revised^n Report on the Algorithmic Language Scheme", where n is the version number of the report. > The pun is a reference to the Algol programming language, which stands for "Algorithmic Language". The naming of Scheme's standards as RnRS is a nod to the "Revised Report on the Algorithmic Language Algol 60", which was the standard defining the Algol 60 programming language. > The hidden pun is in the "Revised^n" part of RnRS. In mathematics, "^" is an operator that denotes exponentiation. So "Revised^n" could be interpreted as "Revised Revised ... Revised", with the word "Revised" repeated n times. This is a playful way of indicating that the language Scheme has been revised multiple times, similar to how Algol was revised to create Algol 60 I couldn't find any direct quote linking the two so I though it was interesting that it still managed to find the link. All I did was paste the quote into the search engine and ask "What's the pun?".
- Filligree 3y agoWhat you're describing isn't a pun. So I'm still in the dark.
- contravariant 3y agoWell, that's on the author for claiming it is a pun, personally I'm happy about the explanation that: - R^nRS is short for Revised^n Report on the Algorithmic Language Scheme - Algol60 was defined in a document called Revised Report on the Algorithmic Language ALGOL 60 - Revised^n is mathematical notation for Revised Revised ... Revised n-times. The prose is a bit iffy, but I'm just happy it managed to find the link between RnRS and Algol 60. It's something I didn't manage to find with just google.
- Jtsummers 3y ago
- sourcepluck 3y agoPersonal opinion upcoming: "WTF" reads petulantly and doesn't suit the subsequent piece at all. I had the strange experience of seeing the title and saying to myself, uh-oh, this will be some gossipy thing, I'll read it anyway just in case it also has some good information on the situation, and maybe I'll be proven wrong too. Which I very happily was! The tone was mature, considered, informative, witty, etc. So I was thrilled to have read it, and more perplexed as to why/how the title ended up there. Now, this is obviously in the purely-subjective category. Perhaps it reads very normally to others, and I just haven't managed to accept how normal "WTF" has become. Just thought I'd share my personal reaction, because the piece was otherwise outstanding, and honest feedback is presumably hard to get. I was thrilled/appalled to learn about the ".io" domain too from perusing further the author's site; great to learn that. Hats off.
- deleted 3y ago[deleted]
- sourcepluck 3y agoI wholeheartedly encourage others to have a browse around the author's other stuff, here's one I loved: http://dpk.io/moderncomputers http://dpk.io/moderncomputers Here's an index of articles: http://dpk.io/articles http://dpk.io/articles
- globalreset 3y agoTL;DR: They can't balance the parenthesis.
- Per_Bothner 3y agoOne of the issues R7RS-large ran into was in how to handle datatypes, such as collection types. Initially, Lisp-style languages had linked lists as the primary data type, but vectors were early added. So you had a "map" function (that worked on linked lists) and "vector-map" (that worked on vectors). Similarly, "length" vs "vector-length". What happens if you want to add more collection types - for example "bytevector"? Do you add "bytevector-map" and "bytevector-length"? Or do you generalize "map" and "length" so they also work on bytevectors (and also vectors)? The former is most compatible with Scheme history and tradition. The latter is IMO preferable going forward as new collection types are added - but it needs some way to talk about frameworks of types that are all sequences (linear collections). I.e. you need at least the concept of inheritance or "interfaces" as used in various languages, including Java and TypeScript. Many languages in the Lisp/Scheme family have some kind of inheritance or interfaces, including Common Lisp, Dylan, Racket, Kawa, and many more. However, this hasn't been standardized for Scheme. R7RS-small has a mechanism to define new data types (records), but they were limited in functionality to C-like structs. I (and others in the community) felt (and feel) that it is premature and unwise to add a bunch of new libraries for new data types until or unless we have some kind of framework for inheritance or interfaces. Others in the community (including the former chair) felt this was unnecessary and perhaps inappropriate for a language with the goals and history of Scheme. There is no clear right answer or consensus for how to go forward, which is part of what caused things to bog down.
- gorset 3y agoThe lack of “interface” was one of the main reasons I never ended up using scheme to build production systems. I loved playing with scheme in my university days 20 years ago, and loved how one can make up any fancy programming concept using call/cc and dynamic-wind. Except if you want to have multiple implementation of some protocol or collection. Hand roll your own object model or dynamic dispatch mechanism? Hard to make it scalable, composable and compatible with other projects.
- deckard1 3y ago> Initially, Lisp-style languages had linked lists as the primary data type, but vectors were early added The Achilles' heel of every Lisp is dealing with any data structure that isn't a linked list. I'm talking aref, setf+aref, vector-ref, vector-set!, char, etc. It's all just a huge pain when compared to any other language (Python, Ruby, JavaScript, Java) that has syntax for arrays, hash maps, strings. Solving the generalized "map" or "length" is really only solving one side of the problem. The other side can't be solved because the language is s-exps and "everything is a function." It would fundamentally cease to be Scheme at that point.
- mrweasel 3y agoSo I know very little about Scheme, other than it's fun to play around with. Wouldn't there be some middle ground where you have a tiny language and a unifying library/plugin system that would allow libraries to work across implementations (given some API/restrictions). So much like we have C++ and Boost or C and various C standard libraries, it would be possible to have any number of small Scheme implementation that could, if the developers wanted to, pull in a larger standard library, of which there could be many. Each Scheme implementation could then opt to develop and distribute a standard library with their compiler or simply refer to any number of third party standard libraries.
- frud 3y agoPlease correct me if I'm wrong here, I'm not trying to insult anyone or start a war. But this is a scheme working group, right? Is scheme really that important today to so many people? I haven't touched lisp since I stopped using EMACS about 10 years ago. I haven't heard about anything interesting involving lisp (except I've heard of clojure) since even before then.
- sourcepluck 3y agohttps://nyxt.atlas.engineer/article/release-3.6.0.org https://nyxt.atlas.engineer/article/release-3.6.0.org Nyxt browser is written in Common Lisp and is going from strength to strength. Think of an attempt to provide the power of Emacs, but built on Common Lisp, and obviously with the graphics and video support browsers have. https://packages.guix.gnu.org/ https://packages.guix.gnu.org/ GNU Guix has 24,207 packages available and is written in Guile Scheme. The name comes from "Guile Nix", as it's based on Nix, so functional packaging, roll-backs, reproducible builds, etc. That might not be your thing, but it's definitely a very active and "successful" operating system. https://shinmera.itch.io/kandria https://shinmera.itch.io/kandria And a last one just for fun, I haven't played it yet but Kandria was written entirely in Common Lisp, and looks very cool.
- eep_social 3y agoThe backend search service for https://flights.google.com/ https://flights.google.com/ is implemented in Lisp.
- comex 3y agoIs it implemented in Scheme?
- eep_social 3y agoNo, lisp, SBCL last I heard
- djha-skin 3y agoR5RS was unanimously decided. R6RS was decided by the majority. What if we just did something where R7RS was decided by 2/3 vote?