News for hackers. Stuff that matters.
Re:Common Lisp in the 21st Century by coldtea on Monday February 10, 2014 @10:39PM (#7215638)
>What does tar mean? ls? df? gunzip (something with guns?)?

How are MORE bad examples an argument against what he says? If anything they reinforce his statement.

Plus, the thing with "tar" and "ls" is that they've been tar and ls in all Unices for decades. If you learn "ls", and maybe "dir" if you want to use Windows, you're golden. Whereas every language seems to use its own names for "princ", "setf" etc, both before and after CL.

Re:Common Lisp in the 21st Century by lispm on Tuesday February 11, 2014 @03:57AM (#7216603)
> How are MORE bad examples an argument against what he says? If anything they reinforce his statement.

These are not bad examples. It is just normal to use short identifiers in many programming languages and command interfaces.

princ is in Lisp for decades. Emacs Lisp:

    ELISP> (princ 'foo)
    foo
Re:Common Lisp in the 21st Century by _pmf_ on Tuesday February 11, 2014 @01:33AM (#7216166)
Maybe his/her point was that this is not a problem that is specific to Common Lisp.
Re:Common Lisp in the 21st Century by kjs3 on Wednesday February 12, 2014 @10:03PM (#7229075)
By that logic, all the other languages are wrong, since CL predates them by decades. Getf has been the same in CL since, what, 1952 (much older than Unix).