Dream metrics:
- How many companies are using Haskell for production / line of business?
- How many developers who use Haskell on a regular basis do those companies employ?
- How many people use Haskell regularly outside of paid work?
- What causes people who are actively trying to learn Haskell to stop?
- How many active participants in Haskell communities are there?
I’m sure there are many more, I have notes with a variety, but that’s the core info I’d love to have.
I think that part of the reason hiring junior Haskellers is not more popular is exactly the difficulties in bringing them up to productivity.
I like the idea of packages for new and promising fields, I have thought about that exact thing. I generally think that we need our tools to get better before we can take advantage of that strategy, though, which is why we picked the one we did first.
Addressing chicken and egg problems like this often mean picking one and going with it for a while, then switching to the other side of the problem. I think that’s likely what we’ll do.