But if you prefer 500 devs instead you should consider ruby, python or PHP. Middle managers are getting high on these numbers.
more expressive languages including common lisp certainly give more power for an experienced engineer to outperform someone fresh out of univeristy. enough to say that I'd rather have 2-3 senior engineers experienced with common lisp or clojure or haskell over 10-15 juniors working on go or python.
and what if you gave them the same expressive language? I'd argue that its even more dangerous. Common lisp is a powerful language but its easy to code yorself into a corner if you don't have the experience to properly use it. it;d be easy to build overcomplicated systems that are brittle. go is in fact better for them because it limits the damage they can cause.
I agree that the hiring pool is small but if you want go level performance, metaprogramming and developer productivity, common lisp was your best option.
Shopify went with ruby. not a terrible language but it did come at teh cost of performance.
What were the options in 2006 for languages with both a fast runtime and reasonable DX? I honestly can't think of any. Ruby at the time was pretty far ahead on DX for mainstream and up and coming languages. It was known to be slow but DX for Java was really not great and mired in "enterprise" features and mindset.
Edit: python was of course around and I don't remember the Django timeline well enough to say if it was viable in 2006 or not. PHP was of course around but again there was a mindset issue at the time.