author | Alan Dipert
<alan@dipert.org> 2020-02-12 22:51:42 UTC |
committer | Alan Dipert
<alan@dipert.org> 2020-02-12 22:51:42 UTC |
parent | 05878bf26050fd24fff5215b4c1fb258d4ea9f4f |
paper/jacl-els-2020.tex | +11 | -4 |
diff --git a/paper/jacl-els-2020.tex b/paper/jacl-els-2020.tex index 9bfcdf9..00bf102 100644 --- a/paper/jacl-els-2020.tex +++ b/paper/jacl-els-2020.tex @@ -320,10 +320,17 @@ Common Lisp environments. Most of the tooling associated with industrial ClojureScript SPAs is developed on the host, as part of a JVM-based compiler toolchain. -ClojureScript's success --- as a mostly static language oriented -around batch compilation and whole-program reloading --- casts the -most doubt on a central claim of this paper: that Common Lisp and -prioritizing interactive development will make SPA development easier. +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. + +Only progress on the JACL project will confirm or disconfirm that +suspicion. In the meantime, JACL development continues in the hope +that at the very least, Lisp-based application development with JACL +will be \emph{at least} as practical and productive as it currently is +with ClojureScript. \section{Design and Implementation}