Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderI've been playing around with a tool to answer the more generic question: why is my binary (written in C, C++, Rust, etc) so large? We use CPU profilers to tell us why our programs are slow. My tool is intended to be a size profiler: why is my program big? It turns out there are some really interesting analyses and visualizations you can perform to answer this question. A few direct comments on the article: - I do not…
Wow, I wrote this 3 years ago and I feel nostalgic. Nowadays I consider this to be obsoleted, as the official Q&A has the exactly same question and many things (especially jemalloc) have been changed in the Rust world. I personally found the HN discussion at that time [1] was greatly fruitful. [1] https://news.ycombinator.com/item?id=11823949
Previous discussion https://news.ycombinator.com/item?id=11823949
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 543
- Total comments
- 241
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2016-06-02 | Why is a Rust executable large?First breakout · Best thread | adamnemecek | 324 | 110 |
| 2016-10-05 | Why is a Rust executable large? | JoshTriplett | 24 | 3 |
| 2019-05-16 | Why is a Rust executable large? (2016)Latest 20+ point return | new4thaccount | 195 | 128 |