What every programmer should know about solid-state drives
Report a link problem
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 feel like maybe this is "what all filesystem developers should now about solid-state drivers"; not very obvious how most other developers would interact with a device at the level of abstraction where they have the kind of necessary control.
I wonder if it's counterproductive to tell every programmer they should know an entire book about SSDs (or DRAM, cf. Drepper), especially when the later chapters tell you that you have no control over the stuff you learned in the earlier chapters due to the FTL and filesystem.
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
- 324
- Total comments
- 141
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 |
|---|---|---|---|---|
| 2015-02-14 | What every programmer should know about solid-state drivesFirst breakout | kozlovsky | 135 | 31 |
| 2017-03-20 | What every programmer should know about solid-state drives | ohjeez | 2 | 0 |
| 2021-09-22 | What every programmer should know about solid-state drives (2014) | quaintdev | 14 | 0 |
| 2022-04-10 | A Summary – What every programmer should know about solid-state drives | kiyanwang | 3 | 0 |
| 2022-05-23 | What every programmer should know about solid-state drives (2014)Hall induction · Best thread · Latest 20+ point return | fagnerbrack | 170 | 110 |