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 order> This is exactly the kind of problem that functional programming was supposed to help us avoid! No, no it isn't. Just like you wouldn't expect 2 * 3 + 8 to suddenly return 22 when you intend it to, you shouldn't expect the order in which you apply functions to not matter. When you pass around a changing state object to every step of your program, you are effectively doing normal imperative programming with global-ish state.
While making the state immutable made it more visible what code was affecting the state, the end result is still multiple pieces of code directly affecting what is essentially a global state. Sure, a copy is passed from one function to the next, but there is still one 'current' state and everything is messing with it directly. The real problem here is not the mutability of the state, it is the ownership of it. Who is responsible for keeping the…
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
- 439
- Total comments
- 183
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-03-29 | Immutability is not enough | pdubroy | 19 | 0 |
| 2016-03-30 | Immutability is not enoughFirst breakout · Best thread | r4um | 271 | 123 |
| 2017-07-04 | Immutability is no silver bullet | prmph | 1 | 0 |
| 2021-06-26 | Immutability is not enough (2016)Latest 20+ point return | jt2190 | 148 | 60 |