To me, that sounds a lot like, when try() is introduced in Go 2, don't use it.

(Though I guess it's a bit harder because you'd have to have your whole team not use it...)

And also all libraries, and community coding habits (which educate new users of the language), and....

"don't use it" is definitely an option, but it's nowhere near "it doesn't exist". It's opting into a constant struggle against the tide.

Code reviews can help. For me, all examples uses of try would be great with properly contextualized error messages ("could not open file" as opposed to "could not read file": it is two very different operations after all!)

At the same time we are surviving the type aliases quite fine (who has ever seen them used? Not me...)

> At the same time we are surviving the type aliases quite fine (who has ever seen them used? Not me...)

You night not have used them directly but you might have benefited indirectly from type aliases. For example, when the "context" package has been moved to the stdlib aliases allowed existing libraries that still used the old "x" context package to be used together with code that used the new package.