Now that’s injecting some sanity back into the move fast and break everything because programming/startup Gods said so circus of today’s programming. Sweet writeup and really good observation.
-
-
-
Thank you!
- Još 1 odgovor
Novi razgovor -
-
-
What bugs me most, the full quote is “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) [...]” The main accent differs.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I'd put it another way. Real performance comes from simplicity first and algorithms second. By the time Knuth said what he said the word Optimization certainly meant what we call now micro-optimization which makes code ugly and incomprehensible which is the opposite of simple.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Да, лет 11 назад нашел первоисточник и вчитался, что же на самом деле говорил Кнут: http://obrizan.blogspot.com/2009/06/blog-post_17.html …
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
You can replace "performance" witha many other -ilities (security, stability,...) and your point is still valid. There's a saying "Security is a concern, not a feature". I think IT applies here aw well. You have to be constantly aware of the performance and trade-offs you make.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
optimization is not necessary about speed. Premature optimisation is about putting too much effort into something without realisation if it makes any sense to do so in the first place.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
"IF you manage to find some huge performance bottleneck and IF altering it would not affect architecture" I have a problem with the second "IF": the most significant speed-ups I remember required architectural changes. Adding a JIT to V8, replacing Dalvik with ART, ...
-
replacing hash-maps with IR in kotlin compiler (not finished). In addition to code clean-up (the first step of green part of
@shipilev's graph), when the programmers rewrite their govnokod, it enables further optimizations, until the new architectural change is required... - Još 2 druga odgovora
Novi razgovor -
-
-
Никита, тебе надо уделить внимание контрастности цветов в твоем блоге! Ссылки вверху очень плохо сделаны. a11y first также важны как и перфоманс, спасибо!pic.twitter.com/409VTPj0K4
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.