satine.org

Safari 4 has entered public beta. It’s blazingly fast (unless you’re using WebKit nightlies already) and has tons of features, even outside of the WebKit core.

Apple’s press release

Some additional notes:

• The Safari 4 Welcome animation is done in HTML5 and CSS Animation. It’s not a video. (Well the compass is) But still very sexy.
• I swiped the welcome animation audio and placed it in this post.
• The Top Sites feature is slick. Those curved preview surfaces are just not ready to be done in CSS Effects.
• CSS Transforms 3D is not available in this public beta.
• Tabs are placed on top. It’s a little harder to drag them around for me when re-arranging, but see if you like them better.
• Safari 4 does not use 1 process per tab contrary to other news reports.

Elaborating on what I wrote (originally for a blog post) in ReadWriteWeb’s Google I/O contest:

In 2009, Google should embed Google Chrome into Google Toolbar, which has a HUGE install base. This would be a huge driver to accelerate Google’s web platform, convert more folks over to a modern browser experience. Imagine a Chrome “Lite” running inside Toolbar inside IE, billed as a “web accelerator”.

I should be clear: Only Google knows how many people have installed Google Toolbar. Even so, I suspect it’s a large number, placing Toolbar on Google’s homepage and paying to 3rd parties like Adobe to bundle Google Toolbar. Google is also very secretive about this number, so it’s got to be either really large, or really small.

Can you imagine what the world would be like if one day most IE users turned into Google Chrome users? Web standards, fast WebKit goodness everywhere.

A web developer can only dream.

Technorati Tags: Google Chrome, Google, Google Toolbar, Internet Explorer, HTML5

A few days after Thanksgiving 2010 actually, with 4 months margin of error.

I just read Greg Linden’s notes on Google Fellow Jeff Dean‘s keynote at WSDM 2009.

Follow my wonderfully flawless math here:

• Google took 10 years to drop their index update latency by a factor of x10000 – from several months to “minutes”.
• Google’s current update latency is “in minutes”. We’ll assume the worst case of 30 minutes (otherwise Jeff might’ve said “under an hour”)
• Assuming linear trends, Google reaches the next speed factor every 8.7 hours.
• If you define “real-time web” as updating once per second, Google will achieve real-time search in 657 days, a little less than 2 years.
• 657 days from Feb 10, 2009 (when Jeff gave his talk) is:
• November 29, 2010.

Google does not fear the Real-Time Web.

Technorati Tags: Google, Real-Time Web, Search, Jeff Dean, Skynet, Twitter, Friendfeed, Echo Chamber