ratings

[cdupont]

Hi,
congratulations for this work. I have a small issue with the ratings: "Best in class" and "Bad" seem to express a judgment on value, while the two others are about maturity. For example some domain could be seen as mature (i.e. well tooled, nothing to do more) but "bad" because Haskell is simply no good at that (e.g. embedded).
Another suggestion: swap "Application Domains" and "Programming Needs" sections, because the reading becomes quickly depressing: already "Immature" at the third bullet...

[Gabriella439]

I'm definitely keeping Application Domains at the top because it's more relevant to most people reading the document. People will forgive deficiencies if you're honest and open about them. It also highlights where the community has room for improvement and has galvanized people to contribute in those areas (such as Data Science, which is a really active area recently)

Generally, maturity tends to correlate with suitability for a domain. For example, if Haskell isn't well suited for a domain, that means less people hacking on tooling or libraries for that domain and therefore less mature.