@aartaka An interesting thought, thanks.
Paolo Amoroso
Posts
-
Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp. -
Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp.@aartaka Thanks, others in this thread report it should work also under
~/quicklisp/local-projects/. -
Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp.@AndreasDavour Right, a local project. Thanks.
-
Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp.@hajovonta Thanks.
-
Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp.Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp. To simplify things and leverage defaults should the source tree go under
~/quicklisp/local-projects/or~/common-lisp/? -
An in-depth analysis of Mozilla's dystopian future.@macinjosh We probably deserve a bit more.
-
An in-depth analysis of Mozilla's dystopian future.@mikro2nd RIP
-
An in-depth analysis of Mozilla's dystopian future.An in-depth analysis of Mozilla's dystopian future.
Again we encounter the fundamental schism of purpose between Mozilla trying to survive, and the mission its core audience believes in.
-
A handy list of the main features of Common Lisp with concise descriptions and code snippets.@vindarel Right, the list is a sort of executive summary of Common Lisp.
-
A handy list of the main features of Common Lisp with concise descriptions and code snippets.@mark_watson What do you like of Quicklisp? Isn't the Python package ecosystem much bigger?
-
Good evening.@synx508 Taking care of labrats.
-
A handy list of the main features of Common Lisp with concise descriptions and code snippets.A handy list of the main features of Common Lisp with concise descriptions and code snippets.
-
Cross-platform GUI frameworks were hot in the 1990s.@mikro2nd Or you can roll your own framework as this developer did in Common Lisp. 😀
https://tomscii.sig7.se/2025/04/The-Barium-Experiment
Jokes aside, I came across those links by reading this post. The author reached similar conclusions to the other posts and yours, but took a different road.
-
Cross-platform GUI frameworks were hot in the 1990s.@mikro2nd This is more recent, 2019:
https://www.hohlerde.org/rauch/en/blog/2019-12-08-GUI-Frameworks/
-
Cross-platform GUI frameworks were hot in the 1990s.@mikro2nd Does this 2016 post help?
https://blog.johnnovak.net/2016/05/29/cross-platform-gui-toolkit-trainwreck-2016-edition
-
@lproven Thanks, I haven't been using Windows since around then and Windows 95.@lproven Thanks, I haven't been using Windows since around then and Windows 95.
-
*Laughs until coughing*@lproven For non Windows users: what does activation do? Register the product with a user ID?
-
Learn Lisp like it's 1972.Learn Lisp like it's 1972. A very early introductory booklet on Lisp that covers a variety of topics, including compilation and garbage collection, and has examples that compare Lisp with Fortran.
-
Quick update of my profile on Codeberg.@thelastpsion Not Psion related but... how do you edit a profile overview on Codeberg?
-
How the Linux-vs-BSD culture clash looked in the 1980s/1990s@lproven Well, my copy of Coherent was version 3.3 for 286 and higher systems but the floppies are now little more than molecules in some landfill. And yes, I wasn't yet aware of the historical significance of such artifacts. If you're interested I can email Stephen Ness.