0:35:04pouarping jackdaniel I'm curious, what is wrong with uiop in McCLIM? Is there some portability issue with it that I'm not aware of? I'm not saying whether McCLIM should use uiop or not, I'm just wondering what the rationale for not depending on it is.
10:48:58jackdanielpouar: from technological issues I have with it: it does not have a clear scope, some things are written suboptimally (i.e run-program is a performance disaster due to "stream slupring"), there is no documentation and it is a preloaded system in asdf. the last issue may seem minor, but if you want to build an image without asdf it becomes a problem
10:49:37jackdanielbecause when uiop is a dependency, it is marked as "satisfied"
10:49:51jackdanieland uiop (i.e from quicklisp) is not downloaded
10:51:23jackdanielthat's from technical issues I have with it (I'm sure I'd find some more). there are more concerns from a social perspective, i.e that main author does not program in CL anymore