Timeline for Is premature optimization really the root of all evil?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 9, 2024 at 6:56 | comment | added | glades | @ShreevatsaR I think the phrase all hinges on the understanding of what "premature" actually is to the programmer. For me this is optimizing without having tested the performance beforehand and actively searching for solutions that are not in your repertoire. If you already know a more optimized version in your head, an optimization is not "premature" if you just apply it. The opposite would be called premature pessimisation which I think is a bigger issue. | |
| Jun 17, 2021 at 6:50 | comment | added | ShreevatsaR | In fact, Knuth is very much pro-optimization (some observations in this tweet and replies)—and he wrote that sentence more in the sense of "sure, sure, I agree premature optimization is bad, let's agree to call it the most evil thing, but look, a careful use of goto in inner loops can give a 12% speedup; why would you give that up?" | |
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot | Commonmark migration | |
| S Oct 27, 2013 at 3:20 | history | answered | Michael Shaw | CC BY-SA 3.0 | |
| S Oct 27, 2013 at 3:20 | history | made wiki | Post Made Community Wiki by Michael Shaw |