> less ugly than a nest of null checks or the equivalent err != nil mess in Go "null checks are ugly and error handling is messy" are your opinions, not object

> less ugly than a nest of null checks or the equivalent err != nil mess in Go "null checks are ugly and error handling is messy" are your opinions, not objective facts. I actually prefer Rust-like enums, but short of that, I think Go's error and nil handling seems quite a lot nicer in practice than Java's `Optional` facilities. Note that these are my opinions, and I'm not posing them as objective facts.