Slashdot Mirror
Google Updates Maps, Makes First Stable Chrome Release Using WebKit Fork
Two bits of Google news from today/yesterday. This morning, Google started rolling out a major update to mobile Maps. They've created a new tablet interface, improved integration with local places, integrated the Zagat guide, and enhanced navigation to automatically route you around traffic incidents. As usual lately, Google also removed a few features: Latitude and Check-ins. If you used those you'll have to use the Google+ application now. They also made a strange change to offline maps: instead of a menu option, you now access the area you want to make available offline and search for "OK Maps." On the Chrome front, Google released Chrome 28 yesterday, the first release featuring the WebKit fork Blink. The under-the-hood changes look promising, quoting the H: "The developers say that the increased speed is also thanks to the new threaded HTML parser, which frees up the JavaScript thread, allowing DOM content to be displayed faster. The HTML parser also takes fewer breaks, which is said to result in time savings of up to 40 per cent."
Hello Google Maps, good bye Apple Maps. Oh wait, why can't I uninstall Apple Maps or change it from being the default?
> The HTML parser also takes fewer breaks
I'm sure there's a better technical explanation for this, but I laughed at the thought of the HTML parser on a coffee break.
XML is a known as a key material required to create SMD: Software of Mass Destruction
It's all KHTML! Never give up dreaming.
Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
Apple doesn't seem to really care very much about Safari on Windows
The fact that they discontinued it should be a clue.
and I hardly think that pages are getting that much more complex every year
Wirth's law, amendment of 2013: web page code get slower faster than browsers get faster.
Ezekiel 23:20
Your mention of caching reminded me of this:
http://www.pclinuxos.com/forum/index.php?topic=113754.0
"In a majority of web browsers, the size of the browser history and document cache is capped in one way or another: for example, if you have not visited facebook.com for a couple of weeks, any record of this will eventually disappear down the memory hole.
This is not the case for Chrome: the browser keeps all the cached information indefinitely; perhaps this is driven by some hypothetical assumptions about browsing performance, and perhaps it simply is driven by the desire to collect more information to provide you with more relevant ads. Whatever the reason, the outcome is simple: over time, cache lookups get progressively more expensive; some of this is unavoidable, and some may be made worse by a faulty hash map implementation in infinite_cache.cc."
That sounds Chrome specific to me.
Certainly I haven't noticed any cache oddities in Firefox, which I tend to leave running for weeks at a time.
-- perl -e'print pack"H*","6e656d6f406d38792e6f7267"'
Google fanboys populate this place. Or as they're known elsewhere, NSA agents.
They also removed the "My Maps" feature where you can pull up maps you've saved under your account within the desktop interface. Sad day for me, I use this for trip-planning all the time.