He said a finnish tech magazine.

I don´t think the finns publish a lot of magazines in english in their own country....

Most phones will not support MAJOR OS upgrades, making their OS "doomed" from a development perspective. Furthermore, why would you invest your time and labour resources in developing an OS upgrade path when it's only ever been released on one phone?
I bought my N900 knowing it was nothing more than a Nokia test bed, knowing that I was nothing more than a crash test dummy for Nokia's decision to implement a phone stack on the Maemo platform as a part of their decision to get things right for the next OS release. One which will never see official support for a device which is already falling behind it competitors in the eyes of most consumers.
why would a company out to make money, keep providing upgrade suppport to an existing device when they can make more money selling you a new one?

It's interesting to note that none of the Symbian ^3 devices we've seen "reviews" of are running production roms/firmware, and are the "glitches" referred to any different to those which are seen on most preproduction handsets? Furthermore, most of the *****ing relates to the fact that S3 looks a lot like earlier flavours. Obviously it's not new and shiny enough for the mindless consumer "experts" (read: anyone with a blog), which is hilarious considering one of the greatest strengths about nokia devices has always been the ability for a user to upgrade to a new phone and be able to start using it straight away, without the steep learning curve.

I've had more random application closures on my HTC Desire than I've had on my N900 and I've been using my N900 a whole lot more than my Desire.

The challenge for phone makers choosing Android will always be relying on a third party to fix the bugs which present on their phones (along with upgrades and the capacity of new OS releases to be able to work on their existing product line up). People will ***** about their crappy LG/Samsung/HTC/SE devices rather than pointing the finger at the 3rd party OS which runs on it.


....was I making a point?......can't remember

I know.

But the product is based in US, an english speaking country. They have much more users there.... whiney users if I may add, which would blog, report and complain about every little problems to 'the web'; I'd expect at least one post that lambasts something that "works really poorly".

who said that the rotation works really poorly? you probably just proved my point about certain bugs being features outside symbian/maemo/meego

You did. Scroll up.
Might want to debug your i/o functions

Ok, Since there's no substance behind that particular post of yours I'm not gonna clutter this thread anymore with this nonsense.

Apparently this is exactly what the WeTab MeeGo tablet does.

But they are much closer to the source of the reality distortion field

It doesn't work "really poorly" nor... even poorly. Glitchy? All rotation on these devices is susceptible to glitching within certain apps, but not all... and if that's a problem that you wish to point to; start by pointing at your device you probably own.

I'm sitting here with an iPhone, Samsung Captivate & Nokia N900... all of them have an app or three that glitch on rotation. On the Captivate, it's Nimbuzz. I can slightly twist my wrist while placing it down. It will rotate or glitch into a rotate/unrotate frenzy every now-and-then. On the iPhone, for me it's textPlus - the ad will rotate first, then the app... and that's when it's on it's back and I tilt it slightly. On the N900, it was during my yesterday usage and trying to answer the damn phone while it was on a table and it got confused which orientation it should be and I almost missed a phone call.

Frustrating, yep. But to the point of a continued finger point and rant against that platform? No. Not unless you want to be petty... or unrealistic.

The manufacturers in question (Nokia, Motorola, HTC) aren't the companies that will be researching those innovations though. That will be done by companies like Sony's battery group, Texas Instruments and Qualcomm, the ones that actually produce the parts. So in the end they'll all improve at roughly the same rate, as the true innovations are abstracted out one more level.

Not quite. It doesn't run as a MeeGo process, but in its own VM. So you have a VM in a VM. This isn't necessarily bad, and the VM is virtualbox so it's open source, but it's not as thin a layer as it could be. I also wonder if the Atom chip used in the WeTab supports hardware virtualization, if not it might be rather slow.

You still can't access the market, so I don't quite see the value.

The developers can put their applications available to "a some other market", or surely there would be other ways to get files downloaded from Android market.

Nokia and Intel should take Java and Dalvik more seriously. C++ and Python are not as flexible and auto-optimizeable when hardware of embedded devices becomes also more complex with multiple CPU cores and more RAM in the future.

Long running applications which use lots of non-persistant dynamic memory are a mess with C++; just look www-browsers (done with C++) and the need of restarting them after few days of running. Lack of intelligent garbage collection in C++ is one of the problems.