Programmers make it all the time too, or at least something very similar. See all those people who are on the endless quest for the "perfect" language, which usually means one which allows for writing the shortest code, sometimes at a very high cognitive cost for very little payoff. No, I really don't want to do a massive amount of mental backflips just to save a few characters, thanks.
To be fair, many programming language enthusiasts understand this and seek languages that properly frame the problems that need to be solved.
Sometimes languages seem to have a high cognitive cost because they expose that the underlying problem has a high cognitive cost. Some things that seem really simple are actually rather complex, like string manipulation and data sharing.
Apparently many programmers keep forgetting that the syntax is just a small part of:
- language itself
- toolchains (compilers, interpreters, AOT, JIT, hybrid)
- differences between implementations and specific behaviour
- libraries, both standard and the most well known third party ones
- IDEs
- build systems and deployment options
- extra tooling for correctness like static analysers
- culture of the people that usually cater for the language
Hence why it is easy to dabble and grasp concepts from multiple languages, but very hard to very quite proficient in a few of them.
If not, you clearly see some gain in more terse syntax.
Seems like a good thing to explore, although perhaps it should not be one's sole focus in life.
Best way to learn a new programming paradigm is by learning a new programming language conducive towards a certain manner of problem-solving.
So yes, I am obsessed with programming languages. But not for the reasons you listed.