Well, Google's C++ Style Guide[1] disallows exceptions, so it makes sense that they wouldn't put exceptions in Go either.
Come to think of it, Go does seem pretty similar to the subset of C++ that Google allows their developers to use. If you think of it that way, it starts to make sense to think of Go as an intended replacement for C++ at Google.
[1]http://google-styleguide.googlecode.com/svn/trunk/cppguide.h...
The Style Guide also says that the decision is mostly due to large amounts of existing Google code that is not exception-safe.
> Things would probably be different if we had to do it all over again from scratch.
Weird. Because I see the opposite.
Go would be fantastic for microservices or targeted applications. But features like exceptions are critical when you have 100+ developers spread across the world working on the one codebase and you want to ensure consistent error handling behaviour across the application.