Of course, when the S can mean either "summer" or "standard" one can forgive some confusion.
You also can't use 'Zulu' from https://en.wikipedia.org/wiki/List_of_military_time_zones either, for that same confusion.
The problem, like with driving, is that humans are communicating the time to humans, instead of the 'smartest' humans having programmed computers how to convey time for the rest of the humans.
UTC != GMT because the former is not a time zone but a time standard. No country uses UTC as a time zone because UTC is not a time zone. All times in the GMT time zone are numerically equal to times expressed in UTC though.
Google is not the arbiter of all things, but a good clue is that Googling "current time GMT" in the summer will give you the time in Britain as though DST didn't exist.
http://www.goodreads.com/book/show/7398826-indians-of-the-oa...
I completely agree with everyone using UTC for numeric time numbering.
I DISAGREE, with remapping 'noon', 'midnight', 'morning', etc. All of the relative descriptions for when in the local solar day a thing is should be approximate local references.
An example: 'lunch' and 'noon' would still be the time in the middle of the local solar day that people get a meal. (Somewhere around 11AM to 2PM in current local times)