I think the "javascript everywhere" phenomenon this article talks about comes from us misjudging the difficulty of learning a new language.
Python's a good example of this (or at least its one I use every day). In order to be able to keep using Python at larger scales, it's become a very big, complex language.
Sometimes I wonder if a lot of use cases for typed Python would be better matched by starting out in a typed language like Go in the first place.
In some ways, learning a new language can be easier than learning lots and lots of features of an increasingly complex language.
Maybe. But the cognitive load of learning a new language (and programming correctly in that language) is real.
And even more real is the emotional stress and mental turmoil a person faces when they're required to learn something new rather than pick up something familiar. When someone has deadlines, a home life, strong demands from their boss, familiarity with build pipelines, a team full of people that they can call on, etc, it's often easier to keep the stress and confusion count lower by sticking to the familiar.
Especially when, in cases like Python with types or Java with Lombok and "just one more thing" will "fix" the rough edges or difficult scenarios that the those specific developers have. Sure it's "one more step", but it's probably a small one and one they can reason about without having to upend their entire mental model (even if in practice they might not need to).
Python's a good example of this (or at least its one I use every day). In order to be able to keep using Python at larger scales, it's become a very big, complex language.
Sometimes I wonder if a lot of use cases for typed Python would be better matched by starting out in a typed language like Go in the first place.
In some ways, learning a new language can be easier than learning lots and lots of features of an increasingly complex language.