 |
| The death of optimizing compilers [pdf] (cr.yp.to) | ||
| recommended by 2 users | 2015 | 217 points by fcambus | compilers | original thread | | ||
| 2 users recommended this thread. What they said: |
| matt_d Oct 10, 2015 | on: Why Intel Added Cache Partitioning | context |
|
kaba0 Sep 30, 2022 | on: Why modern software is slow | context
Well, optimizations need good abstractions to work with. The reason why a SQL query can run much faster than a naive for loop would is precisely due to SQL being very removed from lower-level details. So in extension, optimization is terrible because we might be using the wrong abstraction level? E.g. it is hard to optimize a larger JS program, because if the developer specified some sort of detail it might throw out an entire class of possible optimizations. There is actually an interesting presentation on the topic here: https://news.ycombinator.com/item?id=9396950 , which discusses among others whether a two-way communication between compiler and developer may help. |
| Also recommended by people who recommended this: | ||
| 1. | “As far as the Java platform (AKA ‘the JVM’) goes, Kotlin is painting itself into a corner.” (comment) | |
| recommended by 2 users | 2020 | pron on: Kotlin 1.4 | original thread | | ||
There's been an interesting talk on this a few months ago:
- http://blog.cr.yp.to/20150314-optimizing.html
- (PDF) http://cr.yp.to/talks/2015.04.16/slides-djb-20150416-a4.pdf
Discussions:
- https://news.ycombinator.com/item?id=9202858
- https://news.ycombinator.com/item?id=9396950