*sshole, or when are we finally going to get rid of C?
68 comments · rant
- Comments56
68 comments · rant
Story details from Lobsters ↗ · linked article on sunshowers.io.
*sshole, or when are we finally going to get rid of C? was first seen on Lobsters · Hottest on Nov 7, 2026. Since then it has appeared in 35 checks on 2 different days. Its best position was #1 of 25, reached on Nov 8, 00:51 UTC. It is #10 right now, slipping from #7 to #10 over the last 6 checks. The same link also trended on Hacker News, which raises its cross-platform score.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
▲ as reported by Lobsters.
| List | Best | Days | Checks | Last seen |
|---|---|---|---|---|
| Lobsters · Hottest | #1 | 2 | 35 | |
| YHacker News · Front page *sshole, or when are we going to get rid of C? | same link | |||
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
> There is nothing inherently C-caused in this vulnerability. Nothing is inherently caused by anything, in the sense that you can achieve any desired outcome with any given tool, if you put enough effort into it. Yet, we still say that there are good and bad tools, and similarly, there are languages that make it…
C failed to **prevent** such preventable problem. It doesn't have a type system able to express "this is a failure that the caller *must* handle". Error handling in C is enforced by shaming programmers, which demonstrably is less effective than compile-time errors.
Archived daily, weekly and monthly lists that include this entry.
Yes. As of Nov 8, 14:21 UTC it is #10, slipping from #7 to #10 over the last 6 checks.
#1 on Lobsters · Hottest, on Nov 8, 00:51 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 7, 2026 and has been on the list on 2 days (35 checks) since.