Most of our insults against intelligence come from medical terminology originally. Every word eventually starts being used offensively, and then a new one gets coined and the cycle continues.
Governments have been working on this for more then 20 years now. 40 maybe. As long as I've been alive at least. It's just that all of the actions to try and deal with this have been continuously undermined by fossil fuel industries and right-wing politics.
The fact that Arch is bleeding edge has been an explicit part of the Arch philosophy for as long as I've been using it (for 20 years now). It breaks a lot less frequently than it used to.
And that demonstrates the difference between a developer that is ready for promotion vs one that isn't. You need to be able to make the correct choices for your employer (even if they are not the best choices, or most interesting choices), and being able to recognize these is a skill.
It's fine to prefer the comfort of familiar problems and obstacles, but you shouldn't pretend to yourself that you haven't chosen to embrace them over fear of the unknown.
Instead of talking about skills, or personal efficiency, talk about technologies that you're going to introduce to your product, or some specific difficult problem that you're intending to solve.
Another next career step is to take ownership of things without needing to be asked or told, to create and execute plans, to raise and address problems pro-actively etc. And if your workspace doesn't give you opportunities to do it, and you want career progression, then go somewhere else.
This is bait right? Obviously the answer to this question is there is some population that are happy for there to be suffering so long as it benefits them, and then there is another population that is vehemently against this, and then there is one that is apathetic and tries to just get on with their lives.
This is just not true. The Lisp family contains all conceivable variants of languages, from statically typed Coalton, to dynamically typed Scheme. From functional, immutable by default Clojure to the imperative-style of Common Lisp.
There are prologs, constraint solvers, ffis, JavaScript alternatives, garbage collected and not garbage collected languages that call themselves lisps.
I've seen a few of your comments here today, and generally speaking they are appeals to authority, ad-hominem attacks dressed in allusions to superiority in either knowledge or manners, and truisms without substance. In a manner of speaking: bait. So I guess I'm probably unsurprised if your experience of this is people seeming disagreeble towards you.
I wouldn't argue about things that are a matter of taste normally, except that I've had the experience where I've turned down optimizer settings in order to debug some code better and then the had stack overflow.
Sigh and yet it continues to be true. You can make a pragmatic decision and rely on tail call optimisation for your specific case, but if you are writing a CL library, then it is not idiomatic to use recursion in the same way that you would for Clojure or Scheme.
Even with SBCL, for example, it doesn't have tail-call optimisation for all architectures at all optimisation levels.