News for hackers. Stuff that matters.
Re:The Four Flaws of Haskell by RubyPinch on Monday August 15, 2016 @08:22AM (#12289945)
Probably the whole needing to learn an entire part of English that many didn't even know existed before.

A language really shouldn't require its language-specific glossary to be mandatory reading, just to understand anyone speaking about it. I could just learn any other language in half the time!

from the above comments

> "I have this pure function that I want to apply to the inner value of my functor"

pure function I know well enough, that is the same for any language, functors though... is that a function object that can be applied to something? then why does it already have a value?

I can take terminologies from C, to python, or C#, and feel a-okay, but haskell kinda feels like it went and shut it self away from the world, and its terminology developed differently due to that, I guess.

Re:The Four Flaws of Haskell by 14113 on Monday August 15, 2016 @08:57AM (#12290088)
Haskell terminology is based on the mathematical underpinnings of its type system. It's due to this that those unfamiliar with the maths often have trouble at first grokking the terminology. It's not that Haskell shut itself off, it just draws it's vocabulary from a different source than the other languages.
Re:The Four Flaws of Haskell by RubyPinch on Monday August 15, 2016 @12:50PM (#12291614)
I am aware it didn't invent the words, it was more of a "feels like" statement, as opposed to literal
Re:The Four Flaws of Haskell by greydius on Monday August 15, 2016 @09:57AM (#12290439)
Yeah, this is why I didn't become a surgeon. They have so many invented words for all the different parts of the body and diseases. Seriously, why call something a metatarsal when "foot bone" works just as well?
Re:The Four Flaws of Haskell by JoeAltmaier on Monday August 15, 2016 @09:58AM (#12290445)
Actually, "middle toe bone"
Re:The Four Flaws of Haskell by eggy on Tuesday August 16, 2016 @10:59AM (#12297879)
J is a very functional language used a lot for mathematics and statistical analysis, and it uses more familiar terms for the language like 'verb', 'noun' 'adverb', and 'conjunction' as just some of the terms, as compared with Haskell. J can be very terse, and people don't take kindly to the ASCII character set used as symbols ala APL to perform function composition. It's called line noise in defamatory circles, which is also directed at its cousins K and Kona and others.

Haskell uses a lot of terms specifically from Category Theory. People in the J community are very mathematically inclined, and usually work on different fields of mathematics. I am working on geometric algebra (Clifford Algebra) in J.

I find the J documentation much more friendlier than Haskell's docs.

And J has several IDE's that come bundled with it: JQT - a QT Gui with syntax highlighting, a help section, a minimalist project structure; JHS - a web-based IDE with hooks to D3 vs. the standard plot in JQT; and there is a Python-based IDE (JQide).

There are labs that walk you through chapter-based examples in the interpreter's REPL. One of the newer labs uses videos that go along with the lab in the console, all part of the J ecosystem.

I personally think that Haskell will maintain that purity of purpose, and not get diluted enough to be picked up by the average coder. Even J remains obscure after decades too, but I am hoping that all of the array hoopla (GPUs, big data, machine learning) will bring it to the forefront as a more natural fit, since its native unit and structure is based upon arrays.