The more negative the rating the more I will offer constructive advice for how to improve things.ĭisclaimer #1: I obviously don't know everything about the Haskell ecosystem, so whenever I am unsure I will make a ballpark guess and clearly state my uncertainty in order to solicit opinions from others who have more experience. The more positive the rating the more I will support the rating with success stories in the wild. Immature: only acceptable for early-adopters. Best in class: the best experience in any language.Each programming area will also be summarized by a single rating of either: The topics are roughly sorted from greatest strengths to greatest weaknesses. servers, games, or data science) and the second section covers Haskell's suitability for common general-purpose programming needs (such as testing, IDEs, or concurrency). This post is grouped into two sections: the first section covers Haskell's suitability for particular programming application domains (i.e. The purpose of this post is to discuss both the good and the bad by advertising where Haskell shines while highlighting where I believe there is room for improvement. In this post I will describe the current state of the Haskell ecosystem to the best of my knowledge and its suitability for various programming domains and tasks. See the Conclusions section at the end for more details. Note: This went out as a RFC draft a few weeks ago, which is now a live wiki.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |