More details in the compete post: https://www.tumblr.com/lavenderhorns/705277666010464256/every-now-and-then-i-remember-that-malbolge-exists?source=share
this post was submitted on 07 Mar 2024
486 points (99.2% liked)
Programmer Humor
19623 readers
26 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
"counter-intuitive crazy operation" meh, we already have that, it is called Haskell.
Haskell's crazy operation is intuitive though. Assuming you're talking about
>>=, it's just a generalizedflatMap.This is probably a rather controversial topic in the haskell community. Haskell library and base has a tendency to provide “too many“ infix operator (at least IMO), many of which makes code hard to read for beginners and experts alike.
See the discussion here: https://wiki.haskell.org/Haskell_programming_tips/Discussion#Use_syntactic_sugar_wisely
As a professional Haskell developer, I tend to agree. I loathe any and all lens code I find using a ton of operators (though I just dislike lenses in general). Operators from base are generally fine, but for the rest, just use normal functions damnit. Operators suck for code navigation too.
Yeah, it is one of the problem I have about Haskell.
The other two are lazy evaluation makes print debugging almost impossible, you will need to print the entire environment to figure out where you are.
Finally, I feel like List.fold, state monad, lens are basically just working with mutable structure with extra steps. Although this constructs prevent newbies who are not principled enough to effectively use mutable structure from using mutable structure, but it also doesn't help experienced user to write more effective and clean code.
Mutuabilty are certainly not harmless either. For example in ocaml, if you construct the IntSet type twice, they will be two completely different type. But this behavior can be pretty easily avoided by an experienced user.
What do you feel about these features/shortcomings?
Haskell is abstract, and very different from other popular languages, but I actually find it very intuitive. At the very least, the type system makes it extremely predictable.
I didn't imagine a joke would attract this many people defending Haskell. LOL.
I personally would say I hate Haskell the least among most of the PL I know, maybe except ocaml. Haskell is probably the second if not the most popular programming language (not including proof assistant) in my field, next to Ocaml; and I have been teaching it for couple years. My work is also heavily involved with category theory, so I don't personally mind the category theory jargon.
But all of these doesn't mean Haskell is without its flaws. For this post in particular, I am referring to one of the long standing debate in the haskell community of whether Haskell user and developer has a tendency to overuse exotic infix operators: https://wiki.haskell.org/Haskell_programming_tips/Discussion#Use_syntactic_sugar_wisely
Haha, an actual category theorist! You should have gone with "we have more than one of those in Haskell" or something, then. As it is, it really just reads like someone who thinks higher-order functions are too hard of a concept, and that the whole language is therefore garbage.
welp, karma is not a thing here, nor do I care about them. It is great to see people loving haskell, it is a decent language <3.