News for hackers. Stuff that matters.
Re:Common Lisp Implementations in 2023 by oblio on Thursday February 23, 2023 @10:17AM (#34911644)
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.

Re:Common Lisp Implementations in 2023 by varjag on Thursday February 23, 2023 @02:24PM (#34915128)
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?
Re:Common Lisp Implementations in 2023 by oblio on Friday February 24, 2023 @04:47AM (#34922832)
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.