Thread: Official: No (commercial) MeeGo for the N900
View Single Post
TheLongshot is offline TheLongshot
2010-05-25 , 19:58
Posts: 234 | Thanked: 160 times | Joined on Oct 2009
#178
Originally Posted by gerbick View Post
I think the bitterness of some of the posters in this thread should be equally listened to as much as the happy owners.

The fact that this sounds like the prior iterations which lead to spotty community support - Mer? Despite knowing why, it never happened - or just plain lack of developments and for such an "open source" project, there's enough closed bits that will be either never be opened (BME) or will remain closed enough to cause problems for future support is also sounding like prior iterations.

To sit back and say "Nokia never said MeeGo will be on the N900" actually justifies this type of treatment and Nokia will do it again and again until it stops.

770, N800, N810, now N900. When will it stop with the dead ends and the excuses?
How does this differ from most phone OSs? WinMo has been doing it for years. Android has similar issues, where owners are at the mercy of the manufacturers if they are going to get updates.

Now, I bought my N900 with the full understanding that Harmanhattan/Meego might not come for it. I was fine with that, since the OS runs fine for me for the most part. As long as most major bugs are taken care of, I'm not too worried about my device. As you continue to use your N810, I expect I will continue to use my N900 for a while, particularly if capacitive screens are the future.

Having support for QT 4.6 is bigger for me, since at least we will have a common framework to develop applications between OSs and making the effort for releases more trivial for these OSs. It isn't any guarantee that applications will come, but it does make it more likely, especially from the community level.

If Meego does come, I'll be happy. If it doesn't come, it is likely I'll still be happy, since I'm mostly happy with the phone as it stands now.
 

The Following 2 Users Say Thank You to TheLongshot For This Useful Post: