Mine is that the useState hook is an actual plague on the entire React ecosystem. Regardless of your opinions of React, if you wanna use something then use it right.
this post was submitted on 25 Oct 2026
371 points (95.1% liked)
Programmer Humor
33844 readers
1680 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
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No classes, no mutable types, pure functions where possible (I/O functions exist). I like elixir myself. I use for loops or recursion depending on which is suitable and most understandable. I like the pipe operator because I've gotten used to chaining inputs and outputs like that from Linux CLI.
I prefer functional programming, but also use OO, each their own, but i prefer functional and find it better to write and read
Okay, so... Method chaining, and no refs being passed as params, and structs.
I dislike pure functional programing (not the same as pure functions) because of the boilerplate you need. Want to add a cache? Add a state monad throught the whole pipeline.
Want to have readable code in a six month? Forget it, because you're gonna write in point free style, compositiona without naming inputs and outputs, so that the next time you visit this place, you'll have to check every function for them.