Live data from Hacker News

Common Lisp Implementations in 2023

n16f.net

241–243 of 243 posts

Re: Common Lisp Implementations in 2023

#241
post #173

Earlier quoted context omitted.

Looking at the price of the “Hobbyist DV” version, it is not out of line with what people often spend on hobbies like photography, music, and cycling. Or just on beer and/or wine. Or books. Not to say people don’t spend less on their hobbies, just that a license is a less than a Sony A7R3 or a used Les Paul.

Yes, if a hobbyist absolutely wants to buy a Lispworks license, that should be possible for many people. But that isn't the only criterium. The question is: is anyone as happy to pay the price compared to spend the money on other things, like buying a camera or lens. There is some perception of value involved. For example I do spend a lot of money on my camera equipment and some people are suprised by it, though I sp…

> I struggle to preceive a critical advantage for Lispworks.

CAPI is the reason. If you want to develop a professional GUI application and you want to use Common Lisp, LW is pretty much the only option.

Re: Common Lisp Implementations in 2023

#242
post #173

Earlier quoted context omitted.

Yes, if a hobbyist absolutely wants to buy a Lispworks license, that should be possible for many people. But that isn't the only criterium. The question is: is anyone as happy to pay the price compared to spend the money on other things, like buying a camera or lens. There is some perception of value involved. For example I do spend a lot of money on my camera equipment and some people are suprised by it, though I sp…

> I struggle to preceive a critical advantage for Lispworks. CAPI is the reason. If you want to develop a professional GUI application and you want to use Common Lisp, LW is pretty much the only option.

Depends on what exactly you mean by professional. There are Gtk and Qt bindings for SBCL (haven't tried them), and I have deployed GUI applications in an professional environment based on LTk. Yes, CAPI is certainly a strong point of Lispworks and in a commercial environment, the costs are not necessarily a problem, but I was making the statement in the context of the Hobbyist versions.

Re: Common Lisp Implementations in 2023

#243

It may be worth mentioning that CLASP is one of the only languages/runtime systems that can interoperate with C++ code directly - say, to catch C++ exceptions, or pass around std::vector and so on. It's also quite remarkable that the project was started by a chemistry researcher.

I used to use ECL a bit, and in hindsight I really wish it emitted C++ rather C, even if the generated code was only using C features.

I've used ECL in C++ mode, to interface with ClickHouse (which is a massive C++ codebase).
Post reply on HN