doc VS slimv

- it is possible to subscribe on the changes using RSS (this is a feature of the 40ANTS-DOC documentation builder).

So, the article is harsh on CL: YMMV. Also, your goal may vary: I want to build and ship (web) applications, and so far Julia doesn't look attractive to me (at all). Super fast incremental development, build a standalone binary and deploy on my VPS or ship an Electron window? done. Problem(s) solved, let's focus on my app please.

The author doesn't mention a few helpful things:

- editor support: https://lispcookbook.github.io/cl-cookbook/editor-support.ht... Emacs is first class, Portacle is an Emacs easy to install (3 clicks), Vim, Atom support is (was?) very good, Sublime Text seems good (it has an interactive debugger with stack frame inspection), VSCode sees good work underway, the Alive extension is new, usable but hard to install yet, LispWorks is proprietary and is more like Smalltalk, with many graphical windows to inspect your running application, Geany has simple and experimental support, Eclipse has basic support, Lem is a general purpose editor written in CL, it is Emacs-like and poorely documented :( we have Jupyter notebooks and simpler terminal-based interactive REPLs: cl-repl is like ipython.

So, one could complain five years ago easily about the lack of editor support, know your complaint should be more evolved than a Emacs/Vim dichotomy.

- package managers: Quicklisp is great, very slick and the ecosystem is very stable. When/if you encounter its limitations, you can use: Ultralisp, a Quicklisp distribution that ships every 5 minutes (but it doesn't check that all packages load correctly together), Qlot is used for project-local dependencies, where you pin each one precisely, CLPM is a new package manager that fixes some (all?) Quicklisp limitations

> [unicode, threading, GC…] All of these features are left to be implemented by third-party libraries

this leads to think that no implementation implements unicode or threading support O_o

> most of the language proper is not generic

mention generic-cl? https://github.com/alex-gutev/generic-cl/ (tried quickly, not intensively)

Documentation: fair points, but improving etc. Example of a new doc generator: https://40ants.com/doc/

Also I'd welcome a discussion about Coalton (Haskell-like type system on top of CL).

Great news! Feedback: I guess it's time to start working on documentation ;) The readme doesn't say what the system does. I guess you could maintain a high overview "manually", and in parallel set up a documentation system (40ants doc is kinda cool). Best,

- and 40ANTS-DOC builder.

That is why I've put about half of this year into the Common Lisp documentation generator for all of my libraries.

If you are interested, please read it's docs and join the effort of making good documentation for CL projects: https://40ants.com/doc/

And the doc is built with the new https://40ants.com/doc 🎉 Really cool.

I use Vim with slimv, and have for years.

Maybe you should stick to one new thing at a time. Vim is more than capable of handling Common Lisp. Look at Slimv and Vlime for vim-style SLIME. Focus on CL first. You can come back to Doom / Emacs later.

Neovim works just fine. I use Neoterm to send-to-repl, here's what my config looks like. Your other options include vlime and slimv. I switched to neoterm because it's simple, explicit, and doesn't create unpredictable windows. Works for any other language just as well.

https://GitHub.com/jpalardy/vim-slime is a terrible SLIME to be honest! It is not even a SLIME. It just This does not look like SLIME. It just copies text from one text buffer and paste it to another Vim buffer which is probably running a REPL. "Probably" because who knows what the target buffer is running. vim-slime does not care. This is not Superior Lisp Interaction Mode for $EDITOR (SLIME) in any way.

vim-slime does not connect to any Swank server. It does not understanding Lisp s-expressions. It would happily copy any random text into any random REPL and call it job done! Lisp interaction mode is much much more than just copying and pasting text around. A superior lisp interaction mode gives you live debugging, handling conditions, inspecting variables, navigating the stack frames, ... Vim-slime cannot do anything like this because, well, it just copy-pastes stuff around. Vim-slime is a disingenious and misleading name for a project that is not SLIME.

If you really want to use Vim, do yourself a favor and use https://github.com/kovisoft/slimv and experience a true Lisp interaction mode.

Join me vim brother and don't settle for forcing yourself to use emacs while developing in CL when you don't have to! You even have two vim options! https://github.com/kovisoft/slimv and https://github.com/vlime/vlime with a great comparison of the two: https://susam.net/blog/lisp-in-vim.html

I've seen SLIMV recommended as a SLIME alternative for Vim. Like SLIME, SLIMV is a SWANK client.

I found Vlime to be more updated than slimv and give a smoother experience. With time I've switched to bare neoterm which I highly recommend. CL and lisps in general are designed with a text repl in mind, so this is the method that is guaranteed to work on every obscure CL distribution, and also transfer well to any other REPL-based languages.

If you are already familiar with vim you may want to use slimv

You need Parinfer. Several versions are available for Vim. It's easier to learn than Paredit and works better with Vim-style editing anyway. Lisp emphasizes interactivity with the REPL. It helps if you can send forms you're editing to the REPL for testing. Try something like slimv.