4 ms·

https://www.n16f.net/blog/common-lisp-implementations-in-2023/#lispworks https://www.n16f.net/blog/common-lisp-implementations-in-202...

by kgwgk 4y ago

oblio 4y ago
I've read it and if you're referring to this: > I do not have anything personal against commercial software, and I strongly support developers being paid for their work. But this kind of licensing makes Lispworks irrelevant to everyone but those already using their proprietary libraries. is he wrong? Go ask 100 random devs working for various companies. My money's on 99% on them avoiding those licensing terms in favor of probably anything else.
- kgwgk 4y ago
  In case it was not clear I was referring to this literal quote from the linked article: "The professional and enterprise licenses do not really make sense for anyone" which does indeed convey a more negative tone than this literal quote from the comment that I replied to: "the pricing model which may work for established company ready to invest money from the start"
  - oblio 4y ago
    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.
    - varjag 4y ago
      I think it's a prior that anyone considering the choice of a Common Lisp implementation for production has a preexisting commitment to Lisp.
    - kazinator 4y ago
      What's an example of something that is used for production without preexisting commitment?
      - oblio 4y ago
        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.

https://www.n16f.net/blog/common-lisp-implementations-in-2023/#lispworks https://www.n16f.net/blog/common-lisp-implementations-in-202...

by kgwgk 4y ago

https://www.n16f.net/blog/common-lisp-implementations-in-2023/#lispworks https://www.n16f.net/blog/common-lisp-implementations-in-202...

oblio 4y ago

I've read it and if you're referring to this: > I do not have anything personal against commercial software, and I strongly support developers being paid for their work. But this kind of licensing makes Lispworks irrelevant to everyone but those already using their proprietary libraries. is he wrong? Go ask 100 random devs working for various companies. My money's on 99% on them avoiding those licensing terms in favor of probably anything else.

kgwgk 4y ago
In case it was not clear I was referring to this literal quote from the linked article: "The professional and enterprise licenses do not really make sense for anyone" which does indeed convey a more negative tone than this literal quote from the comment that I replied to: "the pricing model which may work for established company ready to invest money from the start"
- oblio 4y ago
  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.
  - varjag 4y ago
    I think it's a prior that anyone considering the choice of a Common Lisp implementation for production has a preexisting commitment to Lisp.
  - kazinator 4y ago
    What's an example of something that is used for production without preexisting commitment?
    - oblio 4y ago
      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.