Does it feel odd to anyone else that you click the "Request an invite" button and it doesn't ask who you are? Also nowhere on the page does it show my identity.
The New Google Maps
51–60 of 193 posts
Re: The New Google Maps
#52Earlier quoted context omitted.
You should ask for a refund.
"I want my personal information back!" Apologies...
Click on "Close account and delete all services and information associated with it."
Re: The New Google Maps
#53"Request an invite". Dear god, Google still thinking it's a cute little startup. It really is the Microsoft story all over again.
Re: The New Google Maps
#54Re: The New Google Maps
#55Re: The New Google Maps
#56Re: The New Google Maps
#57Re: The New Google Maps
#58What would be really cool is if the intro video/examples was automatically generated using map data from your current location. On another note: it's interesting that it wasn't until I saw this design refresh that I didn't realise just how stale the old design was. It seems like Google revolutionised the maps world when they first released it, and then they let the interface stagnate ever since, so this is nice to se…
I don't really think it was stale or stagnated exactly. You probably saw recently a few posts about how much work goes into them and why exactly they're better than Apple's or Microsoft's. It's very subtle and fundamental stuff. They didn't change much, it's true, but that's because the competition was so bad and they leapfrogged them by so much at the beginning. We'll see how the new look works in action - I can't s…
Re: The New Google Maps
#59Does it feel odd to anyone else that you click the "Request an invite" button and it doesn't ask who you are? Also nowhere on the page does it show my identity.
Perhaps if you don't realize you're logged into gmail. I thought it was well understood that being logged into gmail meant you were logged into all of google's services?
Re: The New Google Maps
#60Earlier quoted context omitted.
It's too bad WebGL isn't usable yet. It's still disabled by default in multiple popular browsers, and in the browsers that have it enabled, it's a security risk (which is precisely the reason why some browsers, such as Safari, don't enable it).
Which security risks are you talking about? In the spec or in the implementations? Currently, the biggest security risk in WebGL is, indirectly, your graphics driver. As an example, the latest security problem with WebGL was in OS X and had to to with exposing uninitialized memory contents. Of course, it is true that graphics driver writers are only now warming up to the fact that a webpage shouldn't cause a kernel p…