As Paul Graham’s blog has been replaying some pretty old posts so have I been reading them. A recent one was the python paradox. I think this applies pretty well to Elm at the moment. The Python Paradox was written in 2004 when Python, was still what one might call an esoteric language, that is, it wasn’t particularly popular. Whereby popular, we mean, used by many people, rather than liked by those that used it. Even at the time Python was very much loved by its users. Anyway the basic idea in the Python Paradox, is that programmers at the time did not learn Python because it was good for their resume, or it was good to find a job, because there were no python jobs. Because of this, it means that they were learning Python purely for the love of programming, and perhaps because Python seemed a bit different. Such programmers are nearly always good programmers, at the very least programmers with potential. Therefore companies should use Python in order to attract such developers, or at least require Python experience.
So it’s a paradox because programmers do not learn Python to get a job, but once companies wise up to this they start seeing Python experience as a major positive, and pretty soon it is a good language to learn if you want a job. Of course, the paradox resolved itself when Python became popular, and mainstream. Now, depending on how you measure it, Python is in the top 3,4, or 5 programming languages for popularity.