Note: Article title is a tounge-in-cheek reference to a recent ARSTechnica article. See below for the real story. It’s actually all about the browser engine and platform, not the OS.

As I begin a series of tests on the Aava prototype phone today, the first thing I wanted to get out of the way was a Sunspider javascript test. It’s CPU-intensive and forms an important part of the chain of events that take place to get a web application displayed on your browser. Yes, it’s one of many variables but it’s a good indicator of CPU performance.

I’ve been recording SunSpider tests for a long time now (feel free to contribute to that list) and have been very impressed by the way that both hardware and software improvements have brought the figures down. In the ARM-based world, the best-in-class devices are producing SunSpider results in less than 10 seconds (iPad, iPhone 4) with some new devices even reaching down to sub 6 seconds [See title reference.] In the world of Intel, netbooks are producing Sunspider results of about 2 seconds (using the latest Chrome build.)

Click to enlarge.

Above is the result for the Aava phone I’m testing at the moment. 4215ms. It runs on Intel’s Moorestown platform at 1.5Ghz and uses the same CPU as you find in netbooks. Running Sunspider on the latest Firefox build on the netbook and the Firefox Mobile build on the MeeGo-based Aava phone you can see the difference is marginal. 4.2 seconds for a prototype phone is quite impressive. The figures confirm the CPU speed and also confirm that the sunspider score is likely to drop to around 2 seconds with the latest Chrome or Android browser build. Try Sunspider on your phone or PC browser to see what score you get. For reference, I use a ultra mobile PC as my desktop PC. It runs a 1.6Ghz Atom CPU and returns a score of about 4.1s. True desktop PCs will come in at below 0.5s

We really are talking PC-power here but there are two things we must not forget. 1) Multi-core ARM-based devices are round the corner too. A dual-core 1.2Ghz Snapdragon platform is likely to reach right down to the 2-3s range. 2) We must also remember that if you were to run this test continuously on these high-power platforms, you are likely to have a dead phone in just a few hours!

MeeGo gets an outing in China this week as Intel takes its developer-focused conference, IDF, to Beijing. As I write this, Intel’s Lynn Wang, Strategic Relationship Manager and Rao Yeleswarapu, a Product Marketing Manager have just finished their talk on MeeGo Technology and Benefits. Danny Zhang, Senior Engineering Manager and Horace Li a Software Engineer with Intel have also given a technical overview talk.

Update: MeeGo 1.0 for Netbooks is now available.

As always, Intel publish the slides from the talks and they contain some great new information. I’ve picked out a few interesting slides from the first presentation which also include the first images of MeeGo’s handheld reference UI for smartphones.

Netbooks.

First off, lets look at the Netbook feature list for MeeGo (we assume 1.0) which confirms a previous tidbit that I picked up from DevMob (that apparently, shouldn’t have leaked.) Mozilla’s browser will be replaced by Chrome (or Chromium, the open source browser.) Quite how significant that if for Mozilla I don’t know but it’s something that should generate quite some discussion.  [Sidenote: There’s been a lot of Google/Intel/Android/Chrome rumors lately. Relationships are definitely good and don’t forget, Intel is part of the OHA. Stay very closely tuned to the Linux Foundation Collaboration Summit which starts tomorrow and runs for three days. Intel, Nokia and Google are all there. I wish I was too but i’ll be glued to the live stream as much as I can.]

You’ll also see that the social messaging app is to be redesigned (the application on Moblin 2.1 very very thin indeed) along with the camera application,email and calendar and date/time app. Best of all, the media application will get an overhaul. Again, the media app on Moblin was extremely basic. Remember that what drops out of MeeGo is not necessarily what you’ll see on netbooks. These code drops (starting with 1.0 in May) are for 3rd partys to take and build on so what you see in V1.0 is not what you’ll see in a final, retail build delivered on a netbook.

In other news, a number of companies have just re-affirmed their support for MeeGo as it transistions out of the Maemo brand. Note that Canonical isn’t in the list. That’s what happens when you move to an RPM-based distro I guess!

Note that the promised touch and gesture support is in there although I don’t see sensor support yet. That’s important for GPS. (It is, however, mentioned in other parts of the presentation.) Also missing is any mention of an application store. Intel’s AppUp is available for Moblin, OVI for Maemo so I wonder if this is simply left out of the core and left up to the OEMs. Remember that happened with Skype on Maemo 5, hopefully that particular relationship, optimisation and integration will spread over to netbooks.

As for netbook eye candy, here’s a snip from the presentation. I don’t know if it’s the proposed 1.0 UI though.

The center column has been dropped from the home zone and filled out with social network tiles. Having used these on Moblin, all I can say is inefficient. 13 status updates on a 1024×600 screen is not an efficient way to use the device for anyone remotely familiar with making friends on the Internet. Let’s hope that the MeeGo UI teams offer an ‘advanced’ front end. Again, it’s not clear if this actually is the UI for release 1.0 though. Update: It is!

Handhelds.

It’s not clear whether this is Intel’s proposal here of if this is 100% agreed between Nokia and Intel but this is what Intel have to say about handhelds using Intel architecture.

As you can see, Fennec, the mobile browser from Mozilla, has been chosen to present the Web. You’ll also get Flash support. Contacts and dialer functions will be integrated (as you’d expect) and there will be VOIP (it will be interesting to see if carriers want that ripped out) and instant messaging. I’m happy to see that the social networking ‘integrated experience’ is mentioned because this is an excellent core feature on the Maemo 5-based Nokia N900. Data sync is also provided along with an LBS app indicating that at least GPS sensors will be supported.

And now for the smartphone eye candy, including cute doggie!

Portrait mode support. N900/Maemo fans rejoice! Note the interesting activity stream in the first picture.
One would assume that emails, tweets and other network events can be included in that stream.

This is typical understated European styling and I bet Nokia were heavily involved here. Personally I love the design but remember, once again this is just a reference design. It’s the sort of UI you’ll see if you take the 1.0 build and drop it on an Aava Moorestown reference design (which I’m trying hard to get hold of) and possibly, the N900. As I said before, I’m not sure if this is Intel’s proposal for the handheld UI or an agreed, across-the-board Nokia/Intel final reference design. We’ll see in May when V1.0 drops.

Timescales.

I mentioned the roadmap on my MeeGo journal a few weeks ago and Intel have re-affirmed those in a nice easy-to-understand slide.

The key date for me is the v1.1 release in the latter part of October. That’s when the MeeGo Summit is likely to occur and it’s right in the Q4 timeframe for product availability. LG GW990, Nokia Nxxx and who knows what else we’ll see. Interestingly, the U.S-based Intel Developer Forum will be in the middle of Sept so it will be interesting to see if Intel and partners have products to announce. October will be a very exciting time and wherever that MeeGo Summit is, i’ll be there!

MeeGo Developers.

You’ve got your very own PDF to browse through too but this slide just smacks me in the face…

‘Cross  App Store Developement’ is something special for devs to consider. The diagram doesn’t actually do the feature justice because it omits to mention the Intel app-store framework that can be used to make branded 3rd-party app stores. One API, many stores, many devices. In a separate presentation on the AppUp store I saw this… line. “World’s largest potential TAM (for a single API) ” When you think of the opportunity there, the mind boggles. Smartphones, Netbooks and the many many devices in-between including home, car and TV.

For more (very) detailed information on the MeeGo stack and the development toolkit, download and read SFTS010 from the content catalogue. (I can’t directly link as it’s a one-time URL used for statistics and tracking.)

all the above slides were taken from the publicly available PDF file SFTS009 available through in content catalogue.

Stay tuned to that catalogue over the next 48 hours as more PDF’s feed in. Particularly interesting could be the Moorestown presentation.