Why you shouldn't use getters and setters on Android

Re:Why you shouldn't use getters and setters on Android by nextw33k on Tuesday October 29, 2013 @08:13AM (#6633447)

That is a very desktop application view. As programmers we should consider CPU cycles equating to battery life.

Whilst it might not have a big impact, if every programmer thought pragmatically about energy usage then the environment as a whole would benefit.

[ Parent | on HN ]

Re:Why you shouldn't use getters and setters on Android by lesiki on Tuesday October 29, 2013 @08:50AM (#6633634)

I think the point is that whatever slowdown the use of Accessor pattern introduces will actually be a lot smaller than 2X, which is useful information when deciding whether to discard the great benefits of using the Accessor pattern that others have mentioned.

[ Parent | on HN ]