ichiran VS common-lisp-standard-library

Check out ichi.moe. The word detection and splitting is quite good, and the backend is available on Github as ichiran. Unfortunately for most sane developers, the backend is written in Lisp.

Here's an example from my codebase which uses a lot of creative naming. There are "suffixes" (which I guess is a grammar term) but also "patches", "penalties", "synergies", "segfilters" and so on which are the terms I made up solely for this code.

You say batteries-included, I see a kitchen sink. Not everything needs huge libraries like ironclad loaded in, and every new dependency is a potential breakage in the future. I like to occasionally look at the dependencies list in my projects' .asd and see if I can get rid of something. For example I used cl-str only for its join function... And then I saw how it's implemented. I mean, really???. I rolled my own join instead. But if everyone starts using these battery-included kitchen sinks, I would still be loading a bunch of libraries I don't ever intend to use. I hear it's a big problem in node.js community.

- Common Lisp has an atrocious documentation culture. People expect you to read code in many cases. (work in progress, but I'm leaving a link here for future readers: https://gitlab.com/mateusz.walas/common-lisp-standard-library).

I'm planning on creating an std.core namespace (that would serve as a basic cl:* replacement to kick off a project / whatever your doing) with a bunch of symbols like lambda, and, or etc, the very often used ones, along with some basic number operations + = - / *. See the readme and/or appropriate files and expect iterations of ideas. If you (the reader) have any questions or ideas or wanna discuss anything related to the project - PM me here on reddit or create an issue in the project.