| Here is a project with about the same number of stars/contributors/contributors with more then 100 lines/time since release https://github.com/graphql/graphql-js/graphs/contributors?fr... :)
So by your logic, i could say: "If this considered a real world javascript/node, it's no wonder there's not a lot of people using it." which is obviously wrong. You are using the wrong metrics to judge the language popularity. Virtually every OSS project has only a handful of core contributors. PS1: Note that i am not arguing PostgREST is a great example of real world haskell, it's not for me to say since i have bias :) PS2: You are right that the source code is not commented and it could use a little of that but what you are missing (because you are not used to haskell) is that a lot of the documentation for haskell projects comes from the types and type signature of the functions. So just by looking at that, in a lot of cases, a haskell programmer can reliably tell what the function is doing without any documentation |
Don't care if it's Python (basically pseudocode), Javascript, Haskell or Erlang.
For all the time Haskell commenters turn criticism into a Socratic dialog, they could be considering ways to make their code digestable. It's been what, 20 years now?
Not just to non-haskell programmers, but all the haskell programmers I see swarming around threads like these on the internet; you'd think they'd actually be teaming up and collaborating with each other. I can't put my finger on it, I think there's a trend, a feeling, that it's not suitable for programmers focused on achieving business ends. It's more of a hobby thing
Programming in the enterprise means confronting the reality that there are design trade-offs and someone else has to read the code. Haskell programmers seem to go off the deep end trying to pull off a hack of making haskell work a certain way, then its "pencils down", sayonara. The real world doesn't accept that, programs have to be maintained by others.