> "It's a very strange move indeed. maps.google.com implies an application lives there, far better than being on the root domain."
How does "maps.google.com" imply an application "lives there" any more than "google.com/maps"?
Technically speaking, "google.com/maps" is far superior to "maps.google.com" (check out the rest of the comments in this thread for examples: simpler DNS configuration, simpler certificate management, CORS, cookies, etc).
How does "maps.google.com" imply an application "lives there" any more than "google.com/maps"?
Technically speaking, "google.com/maps" is far superior to "maps.google.com" (check out the rest of the comments in this thread for examples: simpler DNS configuration, simpler certificate management, CORS, cookies, etc).