I know for a fact that encapsulation is bullshit, and I hate it. My colleagues don't like me anymore, and I lost my job a while ago because of it.
( 29 )
( 256 )
I know for a fact that it was a crappy job, because encapsulation is bullshit. (But class inheritance is worse.)
If encapsulation is bullshit, so is having a door on your bathroom.
Congratulations, this post made it's way to the server through more than just several layers of encapsulation, and you're an idiot
Programmers what a friendly bunch :)
A good compiler will enforce encapsulation at compile time only, a bad, stupid, compiler will put encapsulation enforcement in the runtime code itself. In interpreted environments, encapsulation makes some sense. If you are equating a bathroom to coding, the I can only imagine what your code equates to!
This sounds like it's been put forth by someone who has never had to wade into maintaining a large legacy chunk of code, in which the original authors they shared the same disdain for encapsulation. condemn.
If you lost your job, maybe you should have "ecapsulated" your optionions better :).
Perhaps I should rephrase: If encapsulation is bullshit, so is having a door on a bank vault.
I have to say I envy the original poster, who apparently is capable of keeping all the minute aspects of a complex system in his/her head at once. I'm certainly not that smart, and so I need the crutch of encapsulation to be able to work with large systems and still be effective.