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 orderMap Reduce seems very interesting, but every example I have seen explains it in terms of counting frequency of words in documents. I would love to have someone explain it with an actual business example. I can't think of many real world uses where counting the frequency of words would matter to most businesses. (besides maybe some analysis of log files)
"If homicide, suicide or resigining the job is not an option, how would you solve it?" I would create an n-ary tree (n is arbitrary, maybe 100) from coworkers. The 'leafs' would produce an array of ten numbers based on the blogs assigned to them. Then each node in the tree would take n arrays and sum them up into one array, until me, the root have the final array of ten numbers. First: this is much simpler than what…
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
- 221
- Total comments
- 52
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 |
|---|---|---|---|---|
| 2010-09-30 | Map Reduce: A really simple introductionFirst breakout | guffshemr | 100 | 16 |
| 2012-06-18 | Simple introduction to MapReduce | ninetax | 3 | 0 |
| 2014-05-02 | Map Reduce: A simple introduction (2010)Best thread · Latest 20+ point return | awjr | 117 | 36 |
| 2015-02-08 | MapReduce: a really simple introduction | pajtai | 1 | 0 |