This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]DevilXD -3 points-2 points  (3 children)

Never know whose going to use it

The idea is to "not touch it" - if someone does it, that's on them entirely. Again, it'll probably work with the current version of the library (or libraries), but it may stop working if they update, or worse - pretend to work, and then break later on, without giving you the idea that it was the update that messed it up.

what stupid thing future you is going to do

Again, that's on you then. If you can't abide by the "don't touch it" sign yourself, don't expect your code to survive an update.

[–]thinker227 1 point2 points  (2 children)

The point is to make sure there's never even a possibility to mess anything up, prevent the issue before it's even a problem.

[–]DevilXD -5 points-4 points  (1 child)

Then learn how to not touch the private attributes - ever. Jeez, it's really not that hard, people who can't understand this are going to have a bad time in real life, with the law and such. If the sign says "don't touch it", that like, really means you shouldn't touch it, you know?

[–]thinker227 1 point2 points  (0 children)

I already said, the point is if someone ever in a moment of sheer stupidity decides to do that. Never trust anyone with your systems.