And, as I already posted, it's a rather idiotic one. Does the project member not understand the issue? Kernel support hasn't been removed yet, just the userspace stuff. Last thing we need is to rewrite existing, solid code in JS.
By the converse opinion, if you actually set the privacy settings on Facebook, and Google for that matter, to your comfort level, your data is probably more secure than if you weren't using Facebook or Google etc.
UPDATE: A Microsoft spokesperson has responded to Google saying that:
"Internet Explorer in Windows Phone 8 and Windows 8 use the same rendering engine."
It appears that http://maps.google.com worked fine on Windows Phone until Google started blocking it. In fact it is still working on the Lumia 920 if I go to http://maps.google.co.uk as it looks like they forgot to redirect that one. Are there differences between how it works on Windows Phone and on webkit based mobile browsers? To say that "Since Internet Explorer is not a WebKit browser, Windows Phone devices are not able to access Google Maps for the mobile web" is simply not true. Internet Explorer on the desktop is not a WebKit browser and it works fine with Google maps.
It seems as though the reason that Windows Phone can't access Google Maps is that Google decided (for reasons they would need to explain) to start blocking Windows Phone users.