Re:Common Lisp Implementations in 2023
by kgwgk on Thursday February 23, 2023 @09:56AM
(#34911359)
In case it was not clear I was referring to this literal quote from the linked article:
which does indeed convey a more negative tone than this literal quote from the comment that I replied to:
[ Parent
| on HN ]
Ah, I was looking at the wrong quote.
However, I think techies are too nitpicky.
In casual use "everyone" or "anyone" do not mean: "I literally asked everyone on the surface of the planet".
And he's not wrong.
Unless you have a preexisting commitment to Lisp and ecosystem or your needs are so specific that you need this precise piece of software, you won't use it.
I think it's a prior that anyone considering the choice of a Common Lisp implementation for production has a preexisting commitment to Lisp.
Re:Common Lisp Implementations in 2023
by kazinator on Thursday February 23, 2023 @02:28PM
(#34915194)
What's an example of something that is used for production without preexisting commitment?
Someone who's a language polyglot choosing a programming language for a new system, without external constraints (legal requirements, client mandating tech, closed developer stack, etc).
They have the luxury of choosing the most mature ecosystem.
That kind of person, and there are a fair amount of these around, will look at this kind of enterprise/niche pricing and go that: that's crazy, I'll just use Java/C#/Go/Rust/whatever else.