3 ms·
It's a harder problem when the language is unopinionated. It's easy to bootstrap productivity when everyone is already on the same page about how you write code
by lolinder 5y ago
It's a harder problem when the language is unopinionated. It's easy to bootstrap productivity when everyone is already on the same page about how you write code in this language. Whether it's "OO" or "pythonic", having clear opinions that are baked into the language and shared across the industry means anyone can become productive quickly in a new code base.
The problem that lisp has is that its very expressivity means that most lisp programs are written in their own custom DSL. This is exactly what people love about it but makes knowledge transfer between organizations hard.
- reikonomusha 5y agoMost Lisp programs are not written in their own DSL. Programming teams can be opinionated. Just someone with authority needs to write down the opinions. Common Lisp in particular can be pretty opinionated if everybody shares the same configuration of SLIME and Emacs. There are a few policy rules atop that really make code style consistent and watertight. But, unlike Go, it’s not “for free” with a canonical tool.
- pfdietz 5y ago> Most Lisp programs are not written in their own DSL. Well, except for hu.dwim packages. Pesky Hungarian Common Lisp. :)