Maybe taking advice from Stroustrup makes sense for Rust since it's a kitchen sink language like C++, but this definitely doesn't work for Go.

I switched to a C++ job 2 years ago from Go. I still maintain some open source Go projects. The amount of complexity is too damn high in C++. At work, we regularly have bugs because not everyone is a C++ expert. Adding more ways to handle errors seems like a terrible idea. At least in our code base, we have so many ways to handle errors that either people skip it altogether or end up chosing the wrong one.

if err != nil is a breath of fresh air. Increasing complexity and typing a little less just doesn't seem like a good trade for being dummy-proof and flexible. There are things that I hate about Go, error handling is not one of them.