You can write `Optional`, sure, but you can't un-write `nil`, which is what I really want. I use `Optional<T>` in Java as much as I can, and it hasn't saved me from NullPointerException.
There aren't many possibilities for nil errors in Go once you eliminate the self-harm of abusing pointers to represent optionality.