News for hackers. Stuff that matters.
Re:The Origin of CAR and CDR in Lisp (2005) by lmm on Monday December 26, 2016 @05:29PM (#13260118)
I think people might still start new s-expression based languages, whereas any respectable new language will use head/tail rather than car/cdr.
Re:The Origin of CAR and CDR in Lisp (2005) by dang on Monday December 26, 2016 @06:39PM (#13260355)
I don't know about respectable, but I prefer car/cdr even in a new Lisp. In addition to the composability of the notation, which others have cited, there's the clear lexical symmetry between the two; their compactness, which adds value when writing and reading concise programs; and how easy they are to say out loud. There's something also about their precision: when you say 'car' or 'cdr' in a Lisp context it's immediately clear that there's a linked list at hand and you're talking about it.

The main disadvantage is that they're words with no immediate connection to their meaning, but that's true of many words we're all familiar with. It really only costs anything in the learning stage—which admittedly is a critically important stage. But I think it's fair for a programming language to use specialized idioms for a small number of their most fundamental constructs.

Re:The Origin of CAR and CDR in Lisp (2005) by bluefox on Monday December 26, 2016 @07:34PM (#13260549)
CAR and CDR are also good names because they are part of the Lisp tradition. Also due to this tradition, they have a clear meaning in the context of Lisp. If the "new Lisp" keeps conses (and some may argue that if it doesn't, it shouldn't really fall under "a Lisp"...), perhaps it should also keep these names.
Re:The Origin of CAR and CDR in Lisp (2005) by Turing_Machine on Monday December 26, 2016 @06:03PM (#13260241)
First and rest make more sense if you're only going one level down, true. Long-term Lisp fans will argue that the composability shorthand of caddar, cddddr, cadadar, etc. is just too useful to give up.
Re:The Origin of CAR and CDR in Lisp (2005) by aninhumer on Tuesday December 27, 2016 @09:21AM (#13263241)
I think needing to use such operators is already indicative of inadequate tools to express structure.

And if I did need to use something as complex as `cadadar` frequently for some reason, I'd much rather give it a name (and a type) that expresses what I'm actually doing with it.

Re:The Origin of CAR and CDR in Lisp (2005) by Turing_Machine on Wednesday December 28, 2016 @03:03AM (#13269138)
Well, the point is not that you use cadadar all the time as such, but that you also use cdddar, caadr, and so on, and that having these shorthand forms available means that you don't have to define a whole bunch of one-off functions.
Re:The Origin of CAR and CDR in Lisp (2005) by aninhumer on Wednesday December 28, 2016 @05:28AM (#13269670)
I think saying you can use `cadadar` to operate on a data structure instead of defining an accessor is like saying you can use pointer arithmetic to work with data structures in C instead of using structs.

EDIT: And as other people have mentioned, most serious lisps already have proper tools for building data-structures, so I'm inclined to think that if you're using `cadadar` you're probably doing something wrong.

Re:The Origin of CAR and CDR in Lisp (2005) by Turing_Machine on Thursday December 29, 2016 @01:17AM (#13275950)
"I'm inclined to think that if you're using `cadadar` you're probably doing something wrong."

That's nice. I'm inclined to think that you haven't written very much Lisp code.

Re:The Origin of CAR and CDR in Lisp (2005) by kbp on Monday December 26, 2016 @07:05PM (#13260444)
Conses are arbitrary pairs, not necessarily lists. car and cdr are what eg OCaml and Haskell call fst and snd.