5 ms·
Ask HN: Will the committee that built Common Lisp make a new one in the future?
- nabla9 10y agoNo. ANSI X3J13 committee has been discontinued. It seems that using ANSI to make new standard is unadvisable. The process is cumbersome and there are copyright issues with ANSI. If there is need to revise the standard. Common Lisp folks can for less byrocratic organization to do it. Library standardization can happen organically.
- behnamoh 10y agoIt's too bad, since being a "standard" has helped CL to grow so much, despite some warts that the language inherited from old times habits. Without a standard, it seems most efforts to build a new Lisp come to a naught (think Racket and Clojure and Arc and ...)
- deleted 10y ago[deleted]
- bjt 10y agoClojure seems to be thriving, as far as I can tell.
- shakna 10y agoClojure come to naught? Better tell everyone who is hiring! [0] [0] https://www.indeed.com/jobs?q=clojure https://www.indeed.com/jobs?q=clojure
- masukomi 10y agoyeah, i second this. Clojure is a major success. Depending on how you look at it Racket is a decent success too. It seems to just be more focused on things like helping universities/uni students explore language creation, instead of being a tool for use in businesses.
- RUG3Y 10y agoRacket seems focused on education and experimentation and in that arena I think it's very successful. I'm pretty impressed with where Racket has gone and I think it's very cool.
- jlarocco 10y agoI use CL quite a bit, and disagree with you. The standard was great for removing incompatibilities between all of the old competing Lisps, but now that all of the implementations are on the same page and support the base line standard, I don't see the point in updating and revising the standard. Is there really anything to add that couldn't be done as a library? And while there are warts, it's easy enough to avoid those parts or use macros and libraries to smooth over them. There may be some undefined behavior or implementation specific things in the standard, but it's far less than C or C++, and facilities like the features list makes it pretty easy for libraries to detect implementation differences and do the right thing. > Without a standard, it seems most efforts to build a new Lisp come to a naught (think Racket and Clojure and Arc and ...) Seems like a non sequitur. There are plenty of languages without standards that have become popular (Python, Perl, Java, Ruby, Go, etc.) and also plenty of non-Lisp languages that don't have standards and have gone no where. And then there's ILisp, which has a standard and has still gone basically nowhere.
- kazinator 10y ago> I don't see the point in updating and revising the standard. I'd like to see outstanding issues noted in the existing standard to be resolved. For instance, there is one ambiguity in unwinding. Unwinding occurs under the locus of a dynamic control transfer which has selected an exit point. Unwinding can be intercepted by a form like unwind-protect. That form can "hijack" the control transfer by initiating another one, possibly to a different exit point. The question is: what exit points are still visible and hence available when a given unwind protect cleanup block is executing? Can the unwind-protect choose a less distant exit point than the original control transfer? ANSI CL basically leaves this aspect nonportable: when an unwind protect cleanup is executing, it could be the case that all of the exit points which were "on the way" to the current exit point are already "torn down". Or it could be the case that the implementation performs "tear down as you unwind": exit points are torn down as their binding forms are terminated during unwinding. In a nutshell, it is implementation-defined whether to tear down intervening exit points during the original search for the exit point, or leave them up and take them down during the actual unwinding. The latter behavior is probably less surprising and should probably be ANSI CL standardized.
- kazinator 10y agoThere is a trend that the second and subsequent revisions of ANSI and ISO languages tend to increasingly suffer from major "second system effects".* Instead of just standardizing what is out there, the committees become self-serving; they keep meeting just for the sake of keeping the committee going, and begin inventing things for others to implement. That X3J13 got the job done and then dissolved is very, very respectable. --- * https://en.wikipedia.org/wiki/Second-system_effect https://en.wikipedia.org/wiki/Second-system_effect
- dmichulke 10y agoEven software companies do it. This is the reason we have bloatware.
- oconnore 10y agoThere is no reason to build a second Common Lisp. Those ideas are all fairly well represented, and you only need something new if you're diverging to different ideas: shen or haskell for types and values, julia for method dispatch, or pony for safe concurrency.
- masukomi 10y agoso, there's nothing to improve in CL? My experience seems to be almost diametrically opposed to yours. CL seems a fossil from 20+ ago that hasn't incorporated any of the Computer Science learnings and advancements that have been made since its standardization.
- bykovich 10y agoCan you elaborate?
- lispm 10y agoMonads?
- jerf 10y agohttp://marijnhaverbeke.nl/monad.html http://marijnhaverbeke.nl/monad.html Getting monads into Lisp in a useful way would require the introduction of features that would certainly make it a different language. You may consider this a feature but you'd be arguing with a lot of people who consider it a bug. (I mean that sentence very seriously; no sarcasm, no joke, it is an accurate description of the situation, nor am I implying I would find the idea horrifying... it would simply be a quite significant change to the core type system.)
- bykovich 10y agoAre monads an /advance/, or are they just a language feature that might be nice in some cases, pointless or harmful in others -- like any other feature?
- zokier 10y agoI think most standardization in the LISP sphere happens around RnRS family of standards, ie Scheme.
- erikj 10y agoRnRS are barebone compared to ANSI CL, and the last few versions of Scheme suffered severe resistance from the community.
- convolvatron 10y agodo you think its because they got old and fat? (sorry for being snarky, there is a huge subjective difference between r5 and r6)
- piokuc 10y agoThat's a very good question. I asked this question at a dinner after European Common Lisp Meeting in Madrid in 2013, a wonderful, memorable gig, BTW. I was surprised how unanimous CL elites were on this subject. They were strongly against even small, incremental improvements or additions. IMHO, it would be nice to have a standard socket library, for example. One of the reasons mentioned was cost of the standardization, including updates of all the implementations. I kind of understand it, but, on the other hand, it makes me a bit sad. Things either grow, even very slowly, or become fossil.
- ScottBurson 10y agoYou have to think about this ecologically. What niche would a new CL occupy? What use would anyone have for something similar to CL but not identical? How could such a thing catch on? If the features you think should be added are just extensions, it's very likely they can be added as libraries (though there are occasional exceptions). If they actually change the language so as to break existing code, it's very hard to see why anyone currently using CL would want to use your language. The CL ecosystem is already considered to be behind other major languages in terms of library coverage; your new language would be starting from zero on that point. I think the only way a completely new Lisp would catch on is for some company to create their own, and then to spend enough years using it for enough different things that they create an adequate library on their own -- requiring that they get pretty large. But why would a small company, just starting out, create their own Lisp when they could use CL? (Okay, okay, of course PG did exactly that with Arc. But it's still an unusual choice.) CL is unusually mutable as languages go, anyway. It's even possible for a library to turn it into a subtly but pervasively different language -- I think my functional collections library, FSet [0], is a great example. And of course, this is done without breaking existing libraries. [0] https://github.com/slburson/fset https://github.com/slburson/fset
- kazinator 10y ago> How could such a thing catch on? The way C++11 catches on: implementations update to the standard and it creeps into use.
- ScottBurson 10y agoC++ implementations catch up to the standard because they know there's user demand. The hard thing for a new CL standard would be getting users to care. Do you know of anything a new standard could offer that would attract wide interest?
- kazinator 10y ago- Unicode support - Special characters in string literals via something analogous to \x3F, \177, \n, \t, \u+1234. - Way to write long string literals split across lines with indentation, without involving format: TXR Lisp: (foo bar "this is just one \ \ string literal with only single spaces") - Standardized code walking primitives: one body of user code with no #+this #-that which correctly walks all special forms. - expand-full function: perform all expansion on an expression in a given macro environment. Optionally report all free variable and function references still emanating from the expanded code. - native lazy list via lazy-cons type which satisfies consp. - require numerically equivalent fixnums to be friggin' EQ, damn it. - Overhaul of path names, w.r.t. current OS landscape. One standard way to parse a POSIX or Windows path string to a path name, or a URL. path names should have a :method for this. - Standardize the Meta-Object Protocol for CLOS. - Standard support for weak hash table keys and values. - Hash tables with arbitrary :test function. - GC finalization support: register callback for finalized object.
- dreamcompiler 10y agoI served on NCITS/J13 many years ago when we were trying to decide whether to revise the standard or merely reaffirm the old one. I believe we chose the latter course after many months of discussion but I don't remember why. Was anybody else here on the committee who remembers this? My vague recollection was that there were many directions we could have gone with a revised standard and we couldn't come to a consensus that wouldn't have ended up splitting the community into factions.