News for hackers. Stuff that matters.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by layer8 on Saturday November 12, 2022 @06:18PM (#33578207)
The syntactic consistency is at the same time its downfall: everything looks the same. (Functional languages like Haskell have a similar problem.) It’s more accommodating to human cognition if at least some part of the complexity and diversity of conceptual constructs in programming is represented in the syntax, meaning a certain range of different syntactic constructs that humans can attach meaning to. There is a sweet spot in syntactic diversity that matches the middle of the bell curve across programmers of how human cognition can absorb code. And that sweet spot isn’t on the more “spartan” side where Lisp resides. A different extreme are the more “cryptic” languages like APL and descendants. In a certain way, everything looks the same in those as well.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by bmitc on Saturday November 12, 2022 @07:15PM (#33578611)
I can understand this argument. However, at the same time, S-expressions do allow for rather expressive function names not usually available in other languages. various arrows, question and other punctuation makes, etc. can make for some nice function names.

I do agree with the sentiment to some degree though that it all looks the same. In an aesthetic sense, there is something I do like about it though.

Being a fan of both ML and Scheme, I have actually been experimenting with a syntax that is a hybrid of the two. I’m still in the experimentation phase, but it’s an interesting exercise.

Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by layer8 on Saturday November 12, 2022 @07:24PM (#33578667)
> expressive function names

Yes, but those are effectively library conventions, not fixed properties of the language. Maybe more importantly, names aren’t a structural construct, like a for loop or a class definition. And, arguably, you can have similar syntax in other languages, like e.g. `!` in Rust or the type sigils ($, @) in Perl, except that here you can be sure of their semantics.

Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by bmitc on Saturday November 12, 2022 @08:53PM (#33579158)
The naming is enabled by the way S-expressions work and aren't merely convention. Handling such syntax in non-parenthetic languages is difficult because of the overlap with the other meaning of those infix operators in the language. For example, in F#, if I have a function named `string->number`, then the parser doesn't know if I mean `(string) - (>number)`, `(string-) > (number)`, `(string) -> (number)`, or the function `string->number`.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by layer8 on Saturday November 12, 2022 @09:16PM (#33579282)
I totally understand. What I meant was that the meaning of such names, or the names chosen for a given meaning, is a convention of the library (or set of libraries) that defines the names, and not a semantics the language guarantees, like keywords and punctuation do in other languages. (In Lisp I don't know what `string->number` does any more than I know what `stringToNumber` does.) So S-expressions give you more freedom in the syntax of your function names, but they don't provide more kinds of constructs in the language.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by layer8 on Saturday November 12, 2022 @08:16PM (#33578945)
P.S.: The diversity in programming language design mirrors the diversity in how humans' minds work. Some people work better with dynamic than with static typing. Some people work better with Lisp, some with Haskell or ML, some better with Java and C#, some with APL and friends, etc. There is no one-size-fits-all, and one factor in the adoption of each language is how each programmer's cognition matches the respective kind of language, and also a little bit what they want to achieve practically with the language.

On the one hand it is important to have discussions on the benefits and drawbacks of different approaches in language design, and some people will change their minds some of the time, but it's also an illusion that one single approach will ever suit everyone.

Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by nerdponx on Saturday November 12, 2022 @09:07PM (#33579246)
Human attributes are generally distributed on something like a bell curve. Programming languages with "extreme" characteristics in any direction will almost inevitably be stuck with niche popularity, because they will only be appealing to a small fraction of people. Whereas, even "extreme" people will generally be able to tolerate at least a couple of conventional languages.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by jb1991 on Sunday November 13, 2022 @07:53AM (#33582597)
At issue in this thread is the very definition of extreme vs conventional. The idea in this thread is that the languages now considered to be conventional could have been the niche syntax.