News for hackers. Stuff that matters.
Re:Cloudflare outage on November 18, 2025 post mortem by karel-3d on Wednesday November 19, 2025 @02:24AM (#45976757)
As a gopher I never understand why is there so many unwraps in an average rust code.

Average Go code has much less panics than Rust has unwraps, which are functionally equivalent.

Re:Cloudflare outage on November 18, 2025 post mortem by speedgoose on Wednesday November 19, 2025 @02:37AM (#45976842)
The average golang code segfaults by design.
Re:Cloudflare outage on November 18, 2025 post mortem by richardwhiuk on Wednesday November 19, 2025 @02:27AM (#45976780)
Because Go silently gives you zero/null instead
Re:Cloudflare outage on November 18, 2025 post mortem by karel-3d on Wednesday November 19, 2025 @03:39AM (#45977185)
Idiomatically, it gives you `err` and you do `if err != nil {return err}`. While in rust you mostly do `.unwrap` and panic.

It's not in the type system, but it's idiomatic

Re:Cloudflare outage on November 18, 2025 post mortem by richardwhiuk on Wednesday November 19, 2025 @05:11PM (#45986013)
Get a key from a map and forget to check the error.
Re:Cloudflare outage on November 18, 2025 post mortem by ergocoder on Wednesday November 19, 2025 @02:34AM (#45976824)
which mean an unexpected behavior could go unnoticed for a long time.

I'd prefer a loud crash over that.

Re:Cloudflare outage on November 18, 2025 post mortem by karel-3d on Wednesday November 19, 2025 @03:57AM (#45977307)
Well look at the failure modes in the original article.

In the original PHP code, all worked, only it didn't properly check for bots.

The new Rust code did a loud crash and took off half of the internet.

Re:Cloudflare outage on November 18, 2025 post mortem by j-krieger on Wednesday November 19, 2025 @04:43AM (#45977645)
I love Go and write a ton of it. I've had real segfaults quite a lot.