|
|
|
|
|
by dllthomas
2432 days ago
|
|
That doesn't speak to Haskell. You can say that's because there's not a lot of Haskell and that's likely at least partly true. But the difficulty hiring for a position depends on the number of people qualified and the number of other roles competing for those people. The fact that both of those numbers are smaller for Haskell than (say) Java doesn't tell us whether it'll be easier to hire for Haskell or Java. |
|
Java: 41.1% 36990 developers
JavaScript: 67.8% 61020 developers
Haskell: 0% 0 developers
Jobs:
Java: 73,447 jobs
JavaScript: 59,647 jobs
Haskell: 492 jobs
https://www.indeed.com
Given the numbers, as a hiring manager, I will never ever suggest to any company to try to use Haskell or hire Haskell devs. I know many developers who use it though. They sucessful with what they are doing, turning business problems into Haskell problems and solving those. Sometimes patch the compiler, sometimes write a completely new one. As a tech leader I do not want to have these problems, even if I could hire enough people for projects (which I can't). I always like to read blogs about what is going on though. It satisfies my scientific curiosity but that is it.