Android Performance - 'Avoid Internal Getters/Setters'

Question

Just read this on the dev site:

Avoid Internal Getters/Setters

In native languages like C++ it\'s common practice to use getters (e.g. i = get

Answer 1

Performance wise, there is no difference in accessing this.field or that.field.

The feeling that an instance field is more accessible to the object hosting it is just a syntax illusion.

OO wise, seriously, how complex can an Android app become? Many of the OO mantras are from building monster apps. What's the big deal if your little app uses objects like structs?

And even in a huge app, as long as it's in house, and all source code accessing a field are available for refactoring, there is no problem at all exposing the fields.