Often those who are curious to try Lisp are faced with a number of choices: Which dialect to choose? Which implementation to choose? Which book or tutorial should one follow? Is it necessary use Emacs? SLIME? Here are my recommendations: - Choose Common Lisp because it has been the most popular dialect of Lisp in the overall history of Lisp. It is more convenient than Scheme if one decides to develop serious software…
Portacle makes it all even easier, it's a self-contained package of emagc/SBCL/Slime, etc. with sane defaults https://portacle.github.io/
Common Lisp homepage
11–20 of 313 posts
Re: Common Lisp homepage
#12Often those who are curious to try Lisp are faced with a number of choices: Which dialect to choose? Which implementation to choose? Which book or tutorial should one follow? Is it necessary use Emacs? SLIME? Here are my recommendations: - Choose Common Lisp because it has been the most popular dialect of Lisp in the overall history of Lisp. It is more convenient than Scheme if one decides to develop serious software…
Re: Common Lisp homepage
#13Great site, seems to have a good collection of lisp resources. I am waiting for the documentation to go online, it says it is still parsing the TeX sources of the commonlisp hyperspec. As a side note, I downloaded the Lispworks Common Lisp Hyperspec, but I could only find the HTML version. I see that the project is on Github, maybe someone will parse the Hyperspec and generate the documentation pages. I am adding a r…
Re: Common Lisp homepage
#14What exactly is meant by the line "Design patterns disappear as you adapt the language to your problem domain." The word "disappear" is a hyperlink to a pdf, which refers to domain-specific design-patterns. I don't quite seem to grasp what is being implied on the home-page. Is it something like Lisp is very customizable and allows you to easily overload operators? (I am primarily a Java programmer and have never used…
Re: Common Lisp homepage
#15Often those who are curious to try Lisp are faced with a number of choices: Which dialect to choose? Which implementation to choose? Which book or tutorial should one follow? Is it necessary use Emacs? SLIME? Here are my recommendations: - Choose Common Lisp because it has been the most popular dialect of Lisp in the overall history of Lisp. It is more convenient than Scheme if one decides to develop serious software…
Re: Common Lisp homepage
#16Earlier quoted context omitted.
Portacle makes it all even easier, it's a self-contained package of emagc/SBCL/Slime, etc. with sane defaults https://portacle.github.io/
Can Portacle be used without Emacs? Does it integrate with Sublime Text, Atom or Vim?
Re: Common Lisp homepage
#17What exactly is meant by the line "Design patterns disappear as you adapt the language to your problem domain." The word "disappear" is a hyperlink to a pdf, which refers to domain-specific design-patterns. I don't quite seem to grasp what is being implied on the home-page. Is it something like Lisp is very customizable and allows you to easily overload operators? (I am primarily a Java programmer and have never used…
The short version is that many "design patterns" are de facto macroexpansions. So if you write the corresponding macro, you don't need the pattern any more.
Re: Common Lisp homepage
#18Lisp is quite popular at my current workplace. A few popular open source projects published by our organization have been written in Clojure (a dialect of Lisp that runs on JVM and CLR). A few domain specific languages used internally in our organization are also inspired by Lisp. On a more personal front, I find Lisp to be simple, elegant, and expressive. I use Common Lisp (SBCL) for personal use. Working with Lisp…
Data-point of one here, but I was instantly turned off by the conflation of the empty-list, nil, and boolean-false. I could tell instantly that I'd have a hard time interfacing with data from other real-world systems, so I decided to skip CL and stick to Clojure and various Schemes for my lispy kicks.
Re: Common Lisp homepage
#19Re: Common Lisp homepage
#20In the last 35 years I have probably only averaged using Commin Lisp for about 10% of my development but still love the language.
One problem the Lisp world has is too many fine implementations of dialects of different Lisp languages. I find it impossible to not experiment with most of them.