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> You must not use INTERN or UNINTERN at runtime. I.e. you must not read Lisp data at run time, if it contains symbols, because that will call intern. > You should avoid using a list as anything besides a container of elements of like type. Good-bye, code-is-data. I could reduce this guide by a good 30% with "You should avoid using Lisp as anything as Go or Java". But that could be seen as defining a macro, which you…
Thanks to ITA Software (powering Kayak and Orbitz), Google dedicates resources to open-source Common Lisp development. More specifically, to SBCL: > Doug Katzman talked about his work at Google getting SBCL to work with Unix better. For those of you who don’t know, he’s done a lot of work on SBCL over the past couple of years, not only adding a lot of new features to the GC and making it play better with applications which have alien parts to…
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
- 372
- Total comments
- 175
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-08-10 | Google Common Lisp Style Guide | simonpure | 5 | 0 |
| 2020-07-07 | Google Common Lisp style guideFirst breakout · Best thread | fanf2 | 196 | 120 |
| 2023-08-27 | Google Common Lisp Style Guide | Tomte | 4 | 0 |
| 2024-02-22 | Google Common Lisp Style Guide | swatson741 | 1 | 0 |
| 2024-04-15 | Google Common Lisp Style GuideHall induction · Latest 20+ point return | susam | 148 | 55 |
| 2025-09-30 | Google Common Lisp Style Guide (Revision 1.28) | swatson741 | 18 | 0 |