Mostly just a set of subtly bad ideas. This describes most programming languages. Actually, on average it's usually a bit worse. It's a set of nifty-on-the-sur

Mostly just a set of subtly bad ideas. This describes most programming languages. Actually, on average it's usually a bit worse. It's a set of nifty-on-the-surface ideas which are also subtly bad, which put together result in emergent really-bad. Programming languages are like bands or sports teams. The constituent parts might not be the "best" field leading examples, but put together the whole gestalt can still be awesome. It can help if there's one part which is attention getting, but the whole thing has to "jell." You can implement an OOP system in an FP language. Elixir/Erlang are a good example. Lisp as well. The biggest FP/OOP idea I've seen in my career has to do with awareness around dataflow. If your app is actually about dataflow, then dataflow and explicitly representing the relationships is key. I've seen lots of bad OOP thrown at dataflow, where only few of the relationships are explicit, and you "just have to know" how information gets from one part to another.