5 ms·

No surprise that it's not already implemented because we just throw more cheap hosting and bandwidth at this problem until it's fixed. The "premature optimizat

by jokoon 3y ago

No surprise that it's not already implemented because we just throw more cheap hosting and bandwidth at this problem until it's fixed. The "premature optimization is the root of all evil" misquote really caused a lot of damage to favor growth and profit making instead of better software. It seems programmers have a general habit of just implementing things in the most naive and cheap way and just solve any problem with expensive hardware. We really need a new trend of fast and minimal software because climate change and a finite planet will not allow us to follow Wirth's law for very long.

andrewstuart2 3y ago
The misquote, in my experience, is abusing the "premature" aspect. It's often thrown around as time-based but my understanding of the original quote is that it's all about assumptions rather than data driving complexity in the name of optimization. Optimization should have measurable improvement and the need for it should be demonstrable. Neither of these is harder than writing a benchmark and/or performing some simple math on data measured for that purpose before going about the optimization.
- mcpackieh 3y ago
  The quotes from wikiquote: > "The real problem is that programmers have spent far too much time worrying about efficiency in the wrong places and at the wrong times; premature optimization is the root of all evil (or at least most of it) in programming." and another instance of the same: > "Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. Yet we should not pass up our opportunities in that critical 3%." https://en.wikiquote.org/wiki/Donald_Knuth#Computer_Programming_as_an_Art_(1974) https://en.wikiquote.org/wiki/Donald_Knuth#Computer_Programm... I'm not really seeing much of a "misquote" to be honest. I have always understood this quote to mean that spending too much time micro-optimizing things unnecessarily will waste your time and become a burden to you later. Instead, optimizations should only be performed when the need for optimization becomes manifest.
BodyCulture 3y ago
K8S idling will burn much more CPU than any plain OS, still masses of engineers are following the cult of “burn planet, burn“ like in a zombie distopia. Is this a collective brain failure? Bandy Lee should look into destructive tech trends.
- jokoon 3y ago
  I have never really made extensive use of either docker or k8s, but those things always made me feel weird and I always saw those as some kind of shotgun solution to nightmare-ish software who are so complex, badly written and designed that they requires some kind of hazmat suit to work properly.

by jokoon 3y ago

andrewstuart2 3y ago

The misquote, in my experience, is abusing the "premature" aspect. It's often thrown around as time-based but my understanding of the original quote is that it's all about assumptions rather than data driving complexity in the name of optimization. Optimization should have measurable improvement and the need for it should be demonstrable. Neither of these is harder than writing a benchmark and/or performing some simple math on data measured for that purpose before going about the optimization.

mcpackieh 3y ago
The quotes from wikiquote: > "The real problem is that programmers have spent far too much time worrying about efficiency in the wrong places and at the wrong times; premature optimization is the root of all evil (or at least most of it) in programming." and another instance of the same: > "Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. Yet we should not pass up our opportunities in that critical 3%." https://en.wikiquote.org/wiki/Donald_Knuth#Computer_Programming_as_an_Art_(1974) https://en.wikiquote.org/wiki/Donald_Knuth#Computer_Programm... I'm not really seeing much of a "misquote" to be honest. I have always understood this quote to mean that spending too much time micro-optimizing things unnecessarily will waste your time and become a burden to you later. Instead, optimizations should only be performed when the need for optimization becomes manifest.

BodyCulture 3y ago

K8S idling will burn much more CPU than any plain OS, still masses of engineers are following the cult of “burn planet, burn“ like in a zombie distopia. Is this a collective brain failure? Bandy Lee should look into destructive tech trends.

jokoon 3y ago
I have never really made extensive use of either docker or k8s, but those things always made me feel weird and I always saw those as some kind of shotgun solution to nightmare-ish software who are so complex, badly written and designed that they requires some kind of hazmat suit to work properly.