Timeline for Did the gradual shift in methodology of writing code affect system performance? And Should I care?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 4, 2014 at 6:44 | comment | added | RibaldEddie | Avoiding function calls for performance reasons is absolutely a micro-optimization! Seriously. I can't think of a better example of micro-optimization. What evidence do you have that the the performance difference actually matters for the kind of software that you are writing? It sounds like you don't have any. | |
| Feb 26, 2014 at 15:13 | comment | added | Dennis | Thankx. To drive this a bit towards where I was going, I am not talking about micro-optimization, but a global move towards writing smaller code, incorporating more dependency injection and hence more outside functionality pieces, and more "moving parts" of code in general that all need to be connected together for them to work. I tend to think that this produces more linkage/connector/variable-passing/MOV/PUSH/POP/CALL/JMP fluff at the hardware level. I do also see a value in shift towards code readability, although at the expense of sacrificing hardware-level computing cycles for "fluff". | |
| Feb 26, 2014 at 6:39 | history | answered | mattnz | CC BY-SA 3.0 |