When should you and shouldn't break away from OOP for speed / performance?

Question

In its Android developer articles, Google states that you should usually post public variables, not private ones, with getters and setters to improve performance on embedded devices (I suppose function calls are more expensive than just writing to an address).

I was wondering - to what extent should efficiency be sacrificed in order to adhere to the OOP paradigm? And in what other cases does optimization mean breaking away from “good” coding methods?

Answer 1

Build it for maintenance, and then hack it faster.

, , .

Answer 2

, .

.

Answer 3

, , .

: - . get, , , public OO. , , , .

Answer 4

, , , , , , "". , , , , "". , , , -, " ". , , .

Answer 5

, - . .

- , .

" : . ( !): ". - .

, , . , /, , - ? , , , " ".

Answer 6

, , .

, .

Google , , , API . , / , . , , , - , .

, . , , Java, Fortran.

/ , . , , ressource, , . , Android.. Android, .

Answer 7

? ( MIPS, ).

• [body]
• ( )

/ , CPU reset ( , , , , ). / , . , , / , .

( +).

Answer 8

, Google , .

, , , , , .

, , , , 80% , 20% , . , , , , , Android ).

, Android , . - , , , . , , .

, Google ad absurdum, :

1 XML: 22 000

: 15

, onLayout(), Adapter.getView() inflate(). .

Answer 9

, , . , . Android . , .

, get-get-getter/setter , " ", . , Java, " ", , - .

, ++, , .

Answer 10

, , , .

Answer 11

"" , , . , , . , - , .

; , . , , . , , , , .

Answer 12

Android . - , Android , ( ). . , .

Java , , .

Google , getters/seters Android. / . http://developer.android.com/guide/practices/design/performance.html:

" Getters/Setters

, ++, (, = getCount()) (i = mCount). ++, , , .

Android . , , . - , .

Answer 13

Millions of man hours have been wasted on these stupid little getters and setters. In most cases, they are not needed. Start with open fields, and you can always change their use to get / set methods later if necessary.