Firefox 8 May Catch Up to Chrome for Speed

We’ll see… but I am, at least, hopeful!

Firefox 8 is 20% faster than Firefox 5, matches Chrome 14

“Firefox 8, which only just appeared on the Nightly channel, is already 20% faster than Firefox 5 in almost every metric: start up, session restore, first paint, JavaScript execution, and even 2D canvas and 3D WebGL rendering. The memory footprint of Firefox Seven (and thus Eight) has also been drastically reduced, along with much-needed improvements to garbage collection.

According to our own benchmarks, start up, session restore, and first paint — how long it takes Firefox to appear after you click its icon, and how long it takes to re-open your previous tabs — have been continuously tackled since Firefox 7 first emerged, about two months ago. There’s a 10% difference between Firefox 5 and 7 — and a further 10% speed-up between FF7 and FF8. This isn’t merely an under-the-hood, synthetic-benchmark, on-paper thing either: the difference between FF5 and FF8 is very, very noticeable.

On the 2D canvas front, the huge 20% speed-up is due to the addition of a new graphics backend in Firefox 7 called Azure, which is a unified 2D graphics API that Firefox can use across every platform. At the moment, Cairo handles the interface between Firefox and the host OS’s 2D rendering libraries. Cairo’s performance on top of Direct2D (Windows 7/Vista) is excellent, but it’s not great on either XP or Mac OS X. Azure removes the Direct2D and Quartz (OS X) go-between and allows Firefox to write directly to the underlying 3D subsystems (Direct3D and OpenGL). At the moment, the performance gains are around 20% on Windows — but on OS X, the gains could be even higher. You can follow the Azure implementation on Bugzilla to keep up with the latest changes.”

Google May Yet Release “GDrive”

A cloud based file storage area? Sounds cool, innovative… well, it would have been if Google had rolled it out in 2006! But wait! They might yet!

Google May Be On The Verge Of Resurrecting “GDrive”

“In 2006, Google was internally testing a project codenamed ‘Platypus,’ an online storage service. When it was accidentally disclosed during an analyst meeting as ‘GDrive,’ it quickly captured the web’s imagination. Google seemed on the verge of transforming their servers into our own personal hard drives in the cloud. Plenty of startups were working on this (and still are), but the presumption was that Google would be able to scale this beyond anyone else and do it for free, or very cheap. Google refused to talk about it, but story after story after story kept coming.

Then something weird happened: GDrive never actually launched.

It wasn’t until earlier this year that we found out what happened, thanks to Steven Levy’s book In The Plex. In 2008, GDrive was about to launch under Bradley Horowitz (now a lead on Google+), but Sundar Pichai (now the SVP of Chrome) convinced Google’s top executives not to launch it. The reason? He felt like the concept of a ‘file’ was outdated (sounds more than a bit Jobsian) in the cloud-based universe that Google was trying to build. After some debate, the powers that be at Google agreed and GDrive was shelved, and the team moved over to the Chrome team.

End of story, right? Not so fast.

Something curious appeared this evening in the Chromium Code Reviews issue list. As first noted by Nick Semenkovich on Twitter, there was a ticket to add the URL drive.google.com to a list in the browser’s code. This URL (which is not yet live) lead to a Hacker News thread wondering: ‘Google Drive coming soon?’

Diving a bit deeper into the code reviews, what’s most striking is that drive.google.com doesn’t appear to be referenced anywhere besides this one exposed ticket. This suggests that it’s either no big deal, or that Google is keeping this very secret.

I don’t think it’s the former because the messaging in the one ticket indicates that drive.google.com has been added to the HSTS (HTTP Strict Transport Security) list alongside other key Google apps like docs.google.com and spreadsheets.google.com. Another bit of code puts it alongside Android Market and Google Analytics.

Google information security engineer, Chris Evans, completed the ticket this evening. And Chrome engineer Adam Langley approved it with the message ‘LGTM’ (Looks Good To Me).

I reached out to Pichai (who again, is now a Google senior executive in charge of Chrome), but he declined to comment. A Google spokesperson would only say, ‘The team is always testing out new features, but we don’t have any details to share at this time.'”