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 orderAm I the only one who read it as "Raz-kal" rather than "Raskuhl"
I used to have a job writing Pascal code. I liked it; it was easy to predict how it would behave. It was verbose, but in exchange it was easy to read stuff written by other people. And I've long thought it was a mistake to abandon strong typing. It's good if the compiler (or interpreter, or whatever) can report silly mistakes at the earliest possible stage. (I knows most people disagree, stop with the rock-throwing!) I never tried to…
"But.. why? The author had a C64 as a kid, but never got the hang of understanding proper programming until the x86 era of the 90s. This is his way of mending the hole in is soul. In addition, he hopes that he’ll get filthy rich & famous off this project. Pricing Free of charge. How the “rich” part will be achieved is still up for debate." Seems as valid of a business model as most I see on HN.
Unbelievably Brilliant!
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
- 3
- Total points
- 423
- Total comments
- 95
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 |
|---|---|---|---|---|
| 2019-10-18 | Compiler for the C64: Introducing Turbo Rascal SE | mariuz | 5 | 1 |
| 2019-10-19 | Pascal Compiler for the C64: Introducing Turbo Rascal SEFirst breakout | pjmlp | 112 | 38 |
| 2021-06-27 | Turbo Rascal Syntax Error | ibobev | 101 | 14 |
| 2023-02-06 | Turbo Rascal Syntax Error (TRSE) | mariuz | 2 | 0 |
| 2023-05-07 | Turbo Rascal Syntax ErrorBest thread · Latest 20+ point return | 6581 | 203 | 42 |