10 ms·
I wouldn't call it "objectively bad", but two major warts: - Lack of modules/packages - Dynamic binding as default The former is an annoyance, especially in
by Jtsummers 6y ago
I wouldn't call it "objectively bad", but two major warts:
- Lack of modules/packages
- Dynamic binding as default
The former is an annoyance, especially in a "living system". Contrast with C where the lack of modules and prefix-based naming is controllable by putting things into libraries. So your use of OpenGL functions prefixed with gl is contained in one area, and I never need to see it if my portion deals with network code or anything else. But with elisp, once you load that, all those functions are thrown into the same scope as everything else. If something isn't properly prefixed, or if prefixes collide, then there will be problems.
Dynamic binding (lexical binding can be enabled as an option) means that, coming from other lisps, some things do not do what you'd expect:
(defun make-adder (x)
(lambda (y) (+ x y))
(let ((x 7)
(add-10 (make-adder 10)))
(add-10 x))
With dynamic binding we get 14, with lexical we get 17. This can be addressed by enabling lexical binding, but like I said it's not the default.