> I'd like to see the go team take a radically different approach here playing to Go's strengths - define some framework for presenting web UIs with a Go backend on Android and iOS.

That would be cool, essentially server side rendering of the UI. A number of big players do this, Facebook for one but Spotify too, they've even open sourced the associated iOS framework: https://github.com/spotify/HubFramework. There's also Jasonette, http://jasonette.com, which is actually a lot of fun to experiment with. I've written a few iOS apps for home automation things thanks to Jasonette.

> I'd prefer if they took a step back and prepared a Go 2.0 which removed some of the inevitable cruft (comments as directives, struct tags), and rethought some other features - mostly taking things out rather than adding things, though it would be nice also to see a solution to generics/better containers.

What is it you don't like about struct tags? I've found those to be rather useful when converting between data representations. The comments as directives I assume you mean things like the build tags and generate directives? I like what they enable you to do but I'm not a fan of having those in comments indeed.