I don't think the issue is that the language weaves with the mind (or the reverse). Instead I think there's several issues at play, at least these, and probabl

I don't think the issue is that the language weaves with the mind (or the reverse). Instead I think there's several issues at play, at least these, and probably others: a) mindshare, b) dynamic type systems suck. (b) alone may seem insufficient, since TFA mentions Python as a language that scales, but I've never seen large Python systems -- lots of small Python programs and libraries, yes, but monolythic multi-mloc Python applications? no. When you get to that size, dynamic typing issues become time sinks. As to mindshare, if the number of developers who know Lisp is small, you're not going to get a lot of them. Mind you, you should be able to train them -- once you speak N>3 programming languages, getting to N+1 is not that difficult. But it's a lot easier to hire C++/Java/whatever programmers. This is a mindshare effect. Also, if 1.5 FTEs allows you to build a successful company, then to scale development to 100 FTEs you have to rewrite, well, that's still a success. Many would like to have that problem. And nowadays we're getting good at incremental rewrites as an industry -- witness the Rust effort. I think the future lies with Rust. Rust is a very high-level programming language, but it still lets you get down to the same low level as C. If you sold Rust as a Haskell w/ linear types, no/minimal monads, no I/O monad, and a C-ish syntax -basically, what it is-, I think TFA might run away saying "oh no, another Smalltalk that won't scale". At the very least I'd like to think and hear a lot more about the issue -- whether and why some programming languages do or do not scale teams -- before accepting TFA's conclusion.