Common Lisp

“Modern LLMs have absolutely no issue with writing reasonably good Common Lisp without a kilometer of prompts”

“Each programmer invents their own ad-hoc, undocumented, barely working language in the form of those macros.”

“Lisp is the most unopinionated language there is, therefore it is the worst in terms of lack of decisions encoded in its tooling.”

“Common Lisp is unopinionated, multi-paradigm, but at its core is mutation-friendly, compilation friendly”

“This article convinces me. But I suspect like my lack of domain knowledge of Lisp makes me spend time learning the runtime”

“They excel at Common Lisp—which, ok, has decades of history and documentation which the models have all slurped up.”

“In Common Lisp your program won’t crash, it’ll stop and open a debugger with the whole stack and all the variables.”

“Lisp is the language where you do whatever syntax is suitable for the task, yourself, in an afternoon.”

“Common Lisp often feels designed primarily to implement Common Lisp, rather than to write useful application code.”

“it has by far the best OOB debuggability/introspectability (especially when using SBCL) out of any practical language”

“The regular syntax of Lisp is a tremendous asset when it comes to LLMs being able to work directly in the image.”

“Once you've toiled on the learning curve of Lisp long enough to really grok it you might begin to think you've discovered the foundation material of the universe.”

“just jump into Common Lisp, and finish both Gentle Introduction to Symbolic Computation and Paradigms of Artificial Intelligence”

“bloated at first but in the end you get SBCL, ECL or CCL and almost everything will work the same”

“The interactivity and instant turnaround of a Lisp REPL is still rarely matched in other languages.”

“found a meaty-enough project that ends up being really useful & quite a learning (continuing learning) experience”

“Conditions and restarts and general debugging and repair of the live system, fast startup, native execution speeds”

“CLI, TUI, and desktop GUI apps are basically the only kinds of apps that benefit from CL and can live with its shortcomings”

“a large amount of code written for CL pre-standardization still runs without alteration or with minimal updates”

“None of the functions operating on sequences are generic, so you cannot create your own type and do a `defmethod` and have them automatically adapt to it.”

“Common Lisp it's in places where trying to build such kind of software in C/C++ would be a reciper for disasters.”

“other Lisps are actually slightly better at hot reloading because they're not hampered by the JVM's limits”

“in Common Lisp (I mean just the stuff in the CL spec, no ad-hoc extensions allowed) you can't write anything resembling an OS”

“Common Lisp supports many data structures besides lists, and the same is true of many other Lisps as well.”

“CL lets you recover from exceptions and rewind the stack before reloading your fixes and continuing.”

“I enjoyed learning common lisp, scheme, racket, etc through high school and college and still am fond of them today”

“CL has a pretty anemic type system, but at least it does gradual without having to resort to this.”

“Lisp is expressive enough to read like prose (or like anything else) to as large a degree as required”

“I love how easy it is to be in the flow when writing something that stretches my abilities in Common Lisp”

“You could build systems with much better devx and ux and an order of maginitude less memory usage and wasted CPU cycles.”

“It's not like Clojure or Common Lisp, where a decades old software still runs, mostly unmodified”

“the state of the library ecosystem, documentation, toolchain, and IDEs around them just aren't satisfactory to me”

“I can name an absolute handful of languages I've used that have that flexibility. Common LISP comes to mind.”

“The reason I switched from Scheme to Common Lisp was because I wanted type checking more than I wanted hygienic macros”

“the common Lisp ANSI specification is just awesome, free and locally installable and browsable from Emacs”

“Common Lisp (at least SBCL, which may be the most prolific implementation) is blazingly, scorchingly, stupendously fast.”

“Common Lisp doesn't use (expensive) CLOS dispatch in the core language, e.g. to add two numbers or find the right equality operator.”

“It supports basically all styles which makes it wonderfully useful in whatever domain you happen to find yourself in.”

“have well-specified standards, have stood the test of time and will still be around for decades to come”

“As a GC language Common Lisp is slow as molasses. However, in the realm of languages which are slow as molasses it's got quite acceptable performance.”