*sshole, or when are we going to get rid of C?
hasheddan
35 points
16 comments
November 06, 2026
Related Discussions
Found 5 related stories in 131.3ms across 11,878 title embeddings via pgvector HNSW
- sshole josemrb · 2506 pts · November 05, 2026 · 70% similar
- Show HN: OxiSH, a modern, memory-safe SSH server dochtman · 19 pts · August 13, 2026 · 51% similar
- SSH Sshfighter.com thomasfromcdnjs · 13 pts · August 26, 2026 · 49% similar
- Shitter – A Nitter Fork eustoria · 148 pts · October 23, 2026 · 48% similar
- Late.sh – a command-line Clubhouse for computer people itherseed · 60 pts · July 22, 2026 · 48% similar
Discussion Highlights (4 comments)
zeroCalories
I just really hate rust compile times man
varispeed
What does it have to do with C? It's just poor design. It's like blaming poor driving on one's tracksuit.
whatthejesus
Oohhh there’s one more C vulnerability. Oh my gosh, what ever will I do? Should I buy a new smart toaster? I’m not sure. I just really don’t know what to do right now. It’s called pay attention and f*king upgrade your packages.
PeterWhittaker
This is less a problem with C and more a bad design decision by the musl team. In response to poor practices (programmers not checking what crypt returned), they built an arguably worse one (returning a sentinel value). Sure, Rust's std::result can make it harder to dumb, but dumb can always find a way.