View Single Post
Posts: 515 | Thanked: 259 times | Joined on Jan 2010
#170
Originally Posted by volt View Post
Well, first of all, Qt is anything but new.
I'm not expert on QT but yes it's been around for a long time. Where is this mature / evolved / pervasive and all expansive ecosystem that has changed and revolutionized the industry. They haven't. I mean is there even an QT Store? From what I can see they're still trying to get it to work on MeeGo, Symbian and etc. Sure components exist but while Apple is moving on to iOS 5 and daily adding to the app store, where's QT?

I don't doubt much work and technical problems were solved with QT, but the unfortunate fact is after all these years it's a non-factor and without a QT store / ecosystem (more than just being around years ago) they are for all intents and purposes brand new.

This is the problem with Nokia the past few years. They dabbled in QT, but never really committed. They dabbled in Maemo / MeeGo but never really committed. Now they finally committed to WP7. Bad choice? Too late? Maybe, but the problem is that while Nokia had great technology never utilized it. So I doesn't really matter how long it's been around. Coulda / shoulda only works for geeks. Every day customers want to see the reality not past glory and bragging rights. of who was first.

The Qt strategy was a good one. However, they pulled the plug before they even started to sell the idea to Symbian or multiplatform developers, so it never got tested in real life.
Wait, I thought this was around for years, since 1994. Oh, so they never used it. So what good is technology if it's never used. So you are basically saying though it existed it was never used so for all intents and purposes it was NEW to the industry because it was never really out there.

Just because you warmed up and sat on the bench doesn't mean you were in the game. You can't blame Elop for Nokia's failures. At least he's trying to get in the game by joining the WP team. Promises and fanciful wishing don't win games.

I doubt that the Qt strategy would/could have done anything good about the inherited flaws in Symbian, but it would do very much for the applications on top of Symbian (and thus, MeeGo).
I subscribe to the KISS principle. QT, the one dev. platform to rule them all just was too complicated. With Symbian / MeeGo the big moving target, Nokia thought they'd succeed where Sun failed.

Years ago they had their chance. Too little too late now.

The "Write once and run anywhere" strategy has made Windows the most used operating systems throughout time. Some applications from MS DOS will still work with Windows 7,
backward compatibility is not cross platform

applications will work across virtualbox on cell phones, servers, tablets, tabletPCs, netbooks, pretty much any computer made after the given software were created.
Just because an old dos binary works in Windows 7 doesn't mean its cross platform. Look at what they had to do for XP to get XP based apps to work on Windows 7/ Vista. Show me the Dos application that runs on OSX and linux then have cross-platform.

Oh, and while Sun may have stumbled, Android is nothing but a virtualization motor made in a rip-off copy of Java.
Yes, Java but controlled without all of the problems spreading themselves out too across multiple VMs. I don't see an Android VM for iOS / Bada / WP7 / MeeGo.

So, I think the whole Write once and run anywhere strategy can work very well, thank you vely mush.
Nice try but no. Still have yet to see a credible example that is successful.
 

The Following User Says Thank You to geohsia For This Useful Post: