Totally agreed. Haskell is really big and powerful, and I can see the appeal for the category theory nuts, but this code, for example, doesn't use anything fancy. I'm just using GHC to verify that my code actually conforms to the paradigm, but there's nothing here that couldn't be expressed in JS.
I think there's a definite place for both communities, but beginners (like me) all too often get turned off by the slew of content that's almost entirely irrelevant. Documentation of libraries can be sparse, too, often just amounting to an enumeration of the API. It's not always clear how to start from there, but is useful as you get going.
I'd like to make a more concerted effort to use it pragmatically more often, because it really is fun to do simple things like this. The reason there's no beginner tutorials is that nobody's writing them...but the fix for that is to write 'em :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Totally agreed. Haskell is really big and powerful, and I can see the appeal for the category theory nuts, but this code, for example, doesn't use anything fancy. I'm just using GHC to verify that my code actually conforms to the paradigm, but there's nothing here that couldn't be expressed in JS.
I think there's a definite place for both communities, but beginners (like me) all too often get turned off by the slew of content that's almost entirely irrelevant. Documentation of libraries can be sparse, too, often just amounting to an enumeration of the API. It's not always clear how to start from there, but is useful as you get going.
I'd like to make a more concerted effort to use it pragmatically more often, because it really is fun to do simple things like this. The reason there's no beginner tutorials is that nobody's writing them...but the fix for that is to write 'em :)