And you'll keep hearing it. Step 5 of 5, 6 of 5, 7 of 5. Just because it makes no sense doesn't mean it can't happen. I'm keeping a special kit here that's old but I like it because at some point is says "Installing, 102% done".

Well, I kid, but there's nothing keeping it from happening. Also, this Meego Frankenstein they're building now has a 1.0 label on it that, if not scary enough, consider the fact that it's a marketing ploy. It's real version should be 0.1, not 1.0, as it's never been widely tested, not several builds released, not stable.

And no, after releasing M5, you don't have the right to call untested software "stable", that card has been invalidated. Need I remind you M5 v "1.0" had the wifi bug?

I understand why people want MeeGo. Necessity. As in, if we don't we're buried. Me, I'd much rather see M5 fixed. I am aware that won't happen. So yeah, hurray, let's move forward to 0.1, restart this unpaid beta - sorry, alpha testers stuff, I'm loving it.

Yes, alpha. Beta is when you think it works, you just want a second opinion.

Nokia has no idea how lucky it is. "Using an advertised feature creates a condition that renders the device unusable in 4 hours" is a condition that warrants return.

If firing up my headlights popped a hole in my gas tank I'd use whatever is left to drive back to the dealer. And braking too late.

Such a shame. Excellent hardware, an open OS with limitless possibilities and a potentially huge app base out of the box. A recipe for success. Just let me add a couple of closed, buggy apps and make them undocumented. How did this turn from 98% complete, guaranteed success, to 100% complete, oh-my-god? Only violent shifts could cause such a turn.

What you have here is Venus de Milo with a hole in her head.

There will be. It will be empty.

There's going to be QT Mobility, which I have no grasp of, as a user, not do I care to grasp it. I will NOT have any of the 72 bugs marked as Harmattan, It will also NOT have most of the 2636 bugs that are now open, new, unconfirmed. It will NOT contain most of the top 10 brainstorms. Because all the cool stuff is hard to do.

What feels like a slap is that some people come an implement this between dinner and TV, for free. Like Alarmed, which, minus some fancy graphics, renders all alarm software, ever, obsolete. Like StorageUsage, that renders all storage info, ever, obsolete. The list is extensive.

It will NOT contain sources or clear instructions on how to handle events, or API calls that allows a developer to bypass or replace broken functionality.

It WILL contain inane, easy to do stuff that people left in. Like forgot a letter, missed a link, a pixel is wrong, MicroB loses a keystroke, add a few menus, make themes incompatible again, fiddle with DBus AGAIN, add a few things that should have been there in October and, if you've been really good, suspend all updates for a month, for good measure, because nothing encourages a person who wants to give a gift than not answering the door for a few weeks.

It MAY contain some real fixes, because nobody is perfect. Hey, maybe now Phone won't eat 500% CPU so I can actually answer on tap, instead of sitting there like an idiot, phone ringing, waiting for 5 seconds for the tap to be registered. You'd think a Phone app that is in the ringing state would kind of be prepared to answer.

I've held high, high hopes for 1.2. My hopes for future fixed is dropping exponentially. I'm closing on "meh" for 1.3.

"Hello, this is your captain speaking. Wind is at 5 kph from the west, the weather is sunny, perfect flight conditions. We thank you for choosing Nokia Airlines and remind you that you are flying our new Boeing 747 Beta".