2 ms·
B & C are good points, but... A) Writing a new Common Lisp implementation is a major undertaking, but a new implementation was creates specifically for C++ int
by aidenn0 7y ago
B & C are good points, but...
A) Writing a new Common Lisp implementation is a major undertaking, but a new implementation was creates specifically for C++ interop[1], and that implementation is certainly post javascript being big.
D) Anything targeting JS can run the output through closure; I've done so with Parenscript, for example.
1: https://github.com/clasp-developers/clasp https://github.com/clasp-developers/clasp
- patrec 7y agoA) I'm well aware of clasp, and its a cool project (and post javascript, as well) but it's hardly anywhere near production quality right now (unlike say, clojurescript). So I don't think it's a counters my argument about the CL ecosystem (I'm sceptical that it would make much of a dent even if it becomes a technical success beyond Dr Meister's wildest dreams). D) Of course, but if you require some additional JVM based tooling for a JVM language like clojure, you lose 0% of your potential audience and introduce no additional friction, which is not at all the case for CL (nor would it be for, say C++ or Lua).