What should people know about X over-hyped software/framework/tool/design-pattern/etc?
But in none of these cases am I the only person. Far from it. I'm one of a quiet majority facing a minority of loud zealots.
Note well: Lisp and Haskell are reasonable languages in which one can be quite productive. My issue isn't with the languages per se; it's with the zealots. (I would probably feel the same about Rust, but I haven't bumped heads with as many Rust zealots.)
What should people know? X is useful. X also has flaws. There are other ways to go about it that are also useful, and also have (perhaps different) flaws.
Not a fan of basically anything proprietary / closed source / patent-encumbered either, which is a group that probably includes a lot of popular "stuff". On that note, I don't use any Apple products, as I fundamentally disapprove of their "walled garden" ecosystem approach.
It makes the development experience terrible, introduces a new set of bugs and failure modes you have to consider, and is unnecessary in the vast majority of cases.
Maybe there are some people that legitimately enjoy dealing with this complexity, but for me engineering is simply a tool to solve clients' business problems so I can get paid, and the least engineering I have to do (and my client has to maintain down the line) the better.
I've ranted about this before: https://news.ycombinator.com/item?id=28025934 and https://news.ycombinator.com/item?id=22877650.