What the fuck do you guys have against encapsulation? Don't you know that it's better to define interfaces abstractly rather than concretely, that *what* something does is more important than *how* something does it, so that the implementation can change without users' care?
Name:
Anonymous2009-06-05 19:22
>>14
The problem with encapsulation is that OO faggots tend to want to use at too fine granularity. And since they are all around and your boss will likely be one of them, you'll probably have to endure a lot of baseless nagging if you disagree with them on that.
Name:
Anonymous2009-06-05 22:17
>>10
I think you mean it is licensed under the HMA Pubic License.
Name:
Anonymous2009-06-05 23:01
Encapsulation is nice if it meets these requirements:
1. No "normal" person will ever want to break it.
2. It protects from common mistakes (a = b instead of a == b, etc.).
Name:
Anonymous2009-06-06 0:06
>>17
... what does encapsulation have to do with assignment/equality semantics?
Name:
Anonymous2009-06-06 2:16
>>15
Oh ok. So it's the age old problem of people abusing their tools out of ignorance.