OOP's idea to bundle state and the methods that operate on it together into objects is underrated and also nuanced: nothing stops us applying global methods to global state, but we'd need more identifier prefixes. So it's easier to make related methods and state "mutually local".
-
Show this thread
-
In general, a method can express its action using its parameters, its object's state or global state as input, and its return value, object state or global state as output. The fact that parameters, object state and the return value can be accessed without a prefix is important.
2 replies 0 retweets 8 likesShow this thread -
Replying to @propensive
It really depends on the methods. The issue tends to be people are not great at identifying context boundaries and properly handling state mutation. So safer to have dumb data structures.
1 reply 0 retweets 1 like
There's definitely the opportunity to abuse it, but I think that it encourages the "dumb" way to be good more often than not, on balance. There's an argument, then, that it makes the whole design process dumber, and I'm not sure how to assess that...
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.