Is it now time for this ancient dichotomy to be embraced by computer science?
For the sake of argument, if the principles of OOP are: dynamic dispatch; abstraction; subtype polymorphism; and inheritance, what might be the equivalent for Subject-Orientated Programming ?
In my view, a charateristic of SOP must be that data is personal and unique. Every single usage of data specifies a new unique identifier. To read is to interpret: is to record a new ID. Here, identity (x==y) gets broken; so another operator is needed (x~=y).
somewhat tangential to your point of implementing a so-called SOP, I think the discussion of state, as it relates to OOP or otherwise, can result in very philosophical conversations. see here: http://clojure.org/state
As an ex philosophy major, immutable state and its implications on identity interest me greatly. I feel like this, and other ideas from FP, could be considered a step toward a so-called Subject-Object Programming paradigm.
For the sake of argument, if the principles of OOP are: dynamic dispatch; abstraction; subtype polymorphism; and inheritance, what might be the equivalent for Subject-Orientated Programming ?
In my view, a charateristic of SOP must be that data is personal and unique. Every single usage of data specifies a new unique identifier. To read is to interpret: is to record a new ID. Here, identity (x==y) gets broken; so another operator is needed (x~=y).