Which probably will defeat the point of using Go... its main selling point for me it is its simplicity. If they keep making it more difficult to work with, I might just end up going back to C++
I honestly think you're just being dramatic here, there's no way Go catches up to C++ in that respect any time soon.
On this metric, Go scores 1 (just Go itself), and C++ scores 3 (C preprocessor, C++ itself, C++ templates).
Reflection especially with plugins, are essentially another language that is even more difficult to track down than macros (or templates). Though you can at least write Reflection using go.
I don't think the language as a whole is getting any simpler.
Most language designers generally say that if your language requires a sidecar development environment to be reasonably productive, you've failed at your design tasks. Tools should be time saving helpers, not requirements to understand and navigate even basic code structures.
It will if you mark the alias as deprecated. Unfortunately, there seems to be no standard way to do that in Go.
Preventing it in the first place is a much more effective method.
I was thinking in terms of upgrading a library to a newer version. It’s nice to at least get warnings for everything you’ll need to update, even if it doesn’t make it any easier to actually do so.
...that said, I don't really see the problem either, except in that it will make go less 'simple' to read and understand.