| > As mentioned in the article, the debugger and inspector are key parts of this workflow. Which you can use from the commandline inside of the multiplexor. Like I said it's fully featured because it's just you firing up Steel Bank. The debugger and inspector are still there. > Since there is no versioning dependency management for Quicklisp to leverage, all it can do is try to build your software in isolation, not check compatibility with dependencies, and certainly not runtime compatibility. The lack of versioning and dependency management is pretty dumb I'm not going to lie. I didn't expect that from a package manager. > It's not that software is released too far apart, it's that the release of software is out of the hands of developers, and packaged by a third party with dependencies that may not even be API compatible with the developer's software. Perhaps there are some cases where this is a problem, but in general, I firmly believe that having separate packagers is a good thing[1]. It can be annoying at times, but much more comfortable for the end user. 1: https://drewdevault.com/2019/12/09/Developers-shouldnt-distr... |