> You say inheritance was added to OOP in the 90s. Looking it up, I think I was wrong about that. Early OOP did in fact have implementation inheritance. I gue

> You say inheritance was added to OOP in the 90s. Looking it up, I think I was wrong about that. Early OOP did in fact have implementation inheritance. I guess what I should have said is, OOP originally had three legs. One of them turns out to be bad but the other two seem fundamental to large-scale systems programming. > I'd also like to know why you think REST is disturbingly anti-OOP. So, this is pretty abstract, but REST philosophy seems to put a lot of emphasis on representations of data while discouraging communication of operations on the data. The way to operate on the data is to GET the representation, modify it, and then PUT it back -- not to POST a message saying "please perform operation F". I've heard several hardcore REST advocates specifically argue against communicating operations, deriding it as "RPC" (which I guess they see as derogatory?). In practice I think most people only follow this philosophy when it makes a reasonable amount of sense and ignore it when it doesn't.