The tweet the author quotes says "It's 2021, why aren't you programming in Clojure? It's time." If... you were in a software team, and said... "I think Cloju

The tweet the author quotes says "It's 2021, why aren't you programming in Clojure? It's time." If... you were in a software team, and said... "I think Clojure is the best choice for this project because the talent we have is comfortable with Lisp programming and functional paradigms, we'll be able to deploy with the full featured JVM which is frequently updated and has a ton of libraries, and X and Y, and Z" I think the author would be totally fine with your statement because as he notes in the article, you're taking into account the particular needs you have for your current project and the resources you have available in order to produce something for the end user. The author is saying (in my words) "blanket statements like 'why aren't you using Clojure?' are bad because they create classes within the software community and don't take into account the real world considerations you need to look at when you're building something, you're just creating hierarchy for no reason" Which seems more reasonable. Basically... don't consider yourself great cause you're using Clojure and someone else is using PHP. Instead... consider yourself great for creating value for end users and don't be haughty about your programming language, or stack. Use the tools that are proper for the job instead of making the intern feel like shit cause you're so great at Lisp and they just got out of college with some basic OO skills. I think your comment about "there's no room for language advocates" takes things to a level the author never intended. You can say "I think we should use language X for project Y because of A B and C", that's totally fine. Saying "Wow, you're not using Clojure in 2021? What are you an amateur?" is just kind of a dick statement.