Oh I know it. It's one thing I hate about "the industry" regarding my field: Computer Science. -- There's a lot of companies that want "coders" rather than "software engineers" (the difference being the later solve problems and consider impacts of design, while the former can degenerate into "script kiddies"). It's at the point where if you don't know (or like) C-style languages you're considered 'weird' (perhaps unemployable) though there are easily demonstrable flaws in even at the syntax-level which have been addressed/solved in other languages. (I could give examples, but then it'd become a rant.)
It's a microcosm of the same principle behind the "Graduate's Catch-22", where in order to get entry into a job you need X-years of experience in the field, and in order to get experience in the field you need a job -- it's that companies want cookie-cutter employees, and in order to do that they cannot use "non-standard"* languages/tools even if those tools/languages are better suited to the problems that company is [trying] to address. (See the term technical debt.)
* -- By "non-standard" I mean "less common", not one which lacks a standard.
Story of my life.