> the perspective to appreciate ... basically, clim is like a way to manipulate language objects directly.. so you kind of build an object model & functions in

> the perspective to appreciate ... basically, clim is like a way to manipulate language objects directly.. so you kind of build an object model & functions in lisp, and the ui to manipulate runtime state.. while in a rough sense the same could be said for any gui, with clim + a lisp repl the two are much more tightly coupled - think of it as like a graphical repl sort of thing.. the UI and object definitions can be manipulated while the program is run (each from the other) .. e.g a gui to call a function which generates a new gui based on some modified parameters and then generate a new function becomes possible and even trivial.. as far as base UI or building basic 'applications', no, this will give you buttons, etc just like any other; as for an 'interactive runtime environment', it is quite something else. as for 2018.. this is pretty irrelevant - "Any sufficiently complicated C or Fortran program contains an ad-hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp. "