This vicious cycle exists for a lot of very good languages.
This vicious cycle exists for a lot of very good languages.
I was fortunate enough to be hired in this manner, and I'm always more than happy to help train up new members in a similar fashion. It pays off in the long run—and the short run too, since it doesn't take that long to get somebody playing with Maybes and Eithers in some internal module.
"simply".
So, you have to hire senior Haskell devs and then switch them to teaching new hires. See how this isn't feasible for most companies?
Not saying your approach isn't reasonable, but c suite execs are not always reasonable, and it may be hard to justify this whole setup just to use language X.
If our department has 60 devs across 5-10 teams, the cost of "simply" bringing in people who don't know the language and expecting to both onboard them to business and teach them a new language becomes astronomical
What about "a big company with multiple dev teams that are expected to actually deliver things on time"?