author | Alan Dipert
<alan@dipert.org> 2020-02-12 23:13:10 UTC |
committer | Alan Dipert
<alan@dipert.org> 2020-02-12 23:13:10 UTC |
parent | c24fe58f6f8cba7b34b1cd03ff72f8db2c9a73b6 |
paper/jacl-els-2020.tex | +4 | -3 |
diff --git a/paper/jacl-els-2020.tex b/paper/jacl-els-2020.tex index 6f8a410..1ab0c26 100644 --- a/paper/jacl-els-2020.tex +++ b/paper/jacl-els-2020.tex @@ -324,14 +324,15 @@ Between existing Lisp implementations, it is ClojureScript's success --- as a mostly static language oriented around batch compilation and whole-program reloading --- that renders suspect a central claim of this paper: that Common Lisp and prioritizing interactive development -will make SPA development easier. +will make SPA development in Lisp easier and more practical than it +currently is with ClojureScript. Only progress on the JACL project will confirm or disconfirm that suspicion. In the meantime, JACL development continues in the hope that Lisp-based SPA development with JACL will be \emph{at least} as practical and productive as it currently is with ClojureScript, but -with the added benefit of access to historical Common Lisp-based -techniques. +with the added benefit of the special affordances of Common Lisp's +design combined with access to successful historical techniques. \section{Design and Implementation}