This is the dumbest trope. It’s not the same kind of job, or even very coding-ish, but all the frontends I’ve made are horrifyingly ugly, and I hated making them.
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.
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: wiki.haskell.org/…/Discussion#Use_syntactic_sugar…
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.
My typical attitude is “I was fine without “latest fad” until now, I’ll still be fine now that I still know nothing about it”. And I forget about the whole thing. It’ll probably vanish fifteen months later anyway.
As an aside, who even makes those caricatural, utterly content free websites, and then pats themselves on the back thinking that’s a job well done? They’ve obviously put some amount of work into those things. Is the point to make it seem like it’s a cool super secret society or what?
The ego and audacity to think an AI will simulate you in eternal torment when that would use up precious resources it could be spending on making paperclips.
Most disciplines get more specialized as they evolve. Full Stack goes against that trend, and this meme points at the problem with that. I don’t think it’s going to last.
Overspecialisation can also suck eggs. Interdisciplinary research is trendy in science for the that reason. Even I occasionally read a paper and can see they’re missing some basic fact from another field or subfield that totally undercuts their result.
This was legitimately part of the reason I went with Laminas instead of Laravel for a project. I really don’t want critical documentation to be in video form.
I fully agree with you. However, I just had an interesting thought. Could someone use chatgpt to transcribe the video’s audio to text and plop it into a wiki?
I would say I’m a fairly proficient dev overall, though on this one project I had to work the frontend. It was shit. Everything was shit.
The backend was a steaming pile of crap, and all of the implications of terrible design decisions were offloaded to the frontend. The frontend became the source of every single delay as it was where all crap started to surface. They were ignoring it, so besides frontend communication was also crap. Eventually, in line with ignoring all other issues, they sacked me.
Long story short, backend devs: treat your FE devs well.
A lot of them were shifted 1 second into the future following the problems with the cracked frampton valve on a popular model of felindrical phase felcher.
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.