As someone who is a fan of Common Lisp, this state of the world kind of grinds my gears. "Lisp isn't suitable for large teams because it's too customizable" wh

As someone who is a fan of Common Lisp, this state of the world kind of grinds my gears. "Lisp isn't suitable for large teams because it's too customizable" while it takes me an order of magnitude more time and effort to come up to speed on a new C++ code-base (day job) compared to doing the same on a new CL code-base (hobby). Some of it is tooling: It's trivial to walk through expansions of Lisp macros, while the tooling for C++ is ... less ergonomic to say the least. Some of it is a weird combination of technical/cultural. You can do a lot more in Lisp without reaching for macros as compared to C++ and templates. In addition, every CL style guide ever says "don't use a macro when a function will do." There's also the culture of "Read *Let over Lambda" (a book on Lisp macrology), now don't ever do any of that unless you absolutely have to"