News for hackers. Stuff that matters.
Re:Alpine Linux Security advisory: OpenSSH-server password a... by groestl on Thursday November 05, 2026 @01:35PM (#50382678)
The question is _where_ the error needs to be handled. It's almost never directly at the call site. And then there's a few issues with checked exceptions and Java language things (RMI, closures, etc) which make checked exceptions cumbersome. An exception (checked or not) might be worse than sum types, but they're still a thousand times better then returning an error in-band.
Re:Alpine Linux Security advisory: OpenSSH-server password a... by spullara on Thursday November 05, 2026 @02:56PM (#50383646)
Rust and Go literally have you handle it at the call site by default and if you don't want to you have to pass it on.
Re:Alpine Linux Security advisory: OpenSSH-server password a... by groestl on Thursday November 05, 2026 @06:36PM (#50386142)
Which (at least the way it was done in Go) is ignoring 20 years of experience in programming language design.
Re:Alpine Linux Security advisory: OpenSSH-server password a... by mahboi on Thursday November 05, 2026 @06:41PM (#50386182)
Go doesn't require you to handle it at all. Rust made the right compromise with !
Re:Alpine Linux Security advisory: OpenSSH-server password a... by drdec on Thursday November 05, 2026 @02:57PM (#50383668)
> The question is _where_ the error needs to be handled. It's almost never directly at the call site.

Which is why exceptions in Java can bubble up the stack? You don't have to catch it in a particular method you can let it go to the caller of the method, and so on.

Re:Alpine Linux Security advisory: OpenSSH-server password a... by mahboi on Thursday November 05, 2026 @06:40PM (#50386173)
Checked exceptions must be handled or declared. You end up with everything saying it can throw several random things like IOException.