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> that's the beauty of command line options -- unlike with a GUI, adding these options doesn't clutter up the interface GUIs provide discoverability so often times you don't need a manual. If you don't know how to use a command line tool you must open the manual. So in that way I would consider the man pages as part of the UI and those definitely get cluttered.
Maybe it's because I'm not the biggest Unix purist, but I don't really mind the proliferation of command line options. The two things that do irk me are: * Using short options in scripts. Scripts should almost always use long options. As a corollary, tools should always provide long options unless the tool isn't intended for scripting. * Lack of discoverability. We still don't have a standard way to ask an arbitrary tool which flags it supports, or for a…
Well for one thing, ls needs that many options in order for the joke "What is your name? / What is your mission? / What are three lowercase letters that are not valid options for the xyz version of ls?" to work.
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
- 441
- Total comments
- 297
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 |
|---|---|---|---|---|
| 2020-03-03 | The growth of command-line options, 1979-PresentFirst breakout · Best thread | janvdberg | 248 | 171 |
| 2021-12-15 | The growth of command line options, 1979-Present (2020)Latest 20+ point return | intrepidhero | 186 | 125 |
| 2026-03-06 | The growth of command line options, 1979-Present | teddyh | 7 | 1 |
