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> The system introduces an "amplification" phase where s-expressions are transformed to C code before a traditional build system runs. In other words, this is a compiler. At this point I have to say what I always say: Don't compile to C. You will spend forever eliminating undefined behavior, the debugging experience will be bad because you don't have direct control over the DWARF DIEs, your compilation will be slower for no reason, you will not be able to add…
Good spirit! Interested parties can also hack on Parenscript: it compiles a decent chunk of Lisp to JavaScript, it's extremely well documented, and even has a CLOS like object system. http://common-lisp.net/project/parenscript/ Regards. - someone who compiles lisp to native object code
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
- 254
- Total comments
- 144
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-01-23 | Amplifying CFirst breakout | cesare | 112 | 43 |
| 2016-02-07 | Amplifying C (2010)Best thread · Latest 20+ point return | jhack | 140 | 101 |
| 2020-07-28 | Amplifying C (2010) | tosh | 2 | 0 |