|
2010-10-27
, 05:01
|
|
Posts: 4,384 |
Thanked: 5,524 times |
Joined on Jul 2007
@ ˙ǝɹǝɥʍou
|
#2
|
|
2010-10-27
, 05:27
|
Banned |
Posts: 974 |
Thanked: 622 times |
Joined on Oct 2010
|
#3
|
He is, isn't he?
But I thought FOSS is also partially about sticking it to da man?
|
2010-10-27
, 07:13
|
Posts: 289 |
Thanked: 560 times |
Joined on May 2009
@ Tampere, Finland
|
#4
|
Very good read
http://asia.cnet.com/reviews/mobilep...2204005,00.htm
MeeGo is the future for Nokias smartphones. At least that is the plan, but making good plans has never been a problem for Nokia, they need to execute and deliver as well.
The N9 will run Maemo with a "MeeGo" UX. But the (Maemo)MeeGo UX will not be the UX that is going to be used on real MeeGo phones. Nokia will not encourage people developing for that UX, but will instead encourage developing on Qt and Qt Quick. This will probably be just fine, but think about all the wasted work: Symbian4 UX wasted, Maemo\MeeGo UX wasted. Strange indeed.
As I understand, Intel MeeGo for handsets is as good as finished, ready for prime time. Why don't Nokia simply go fwd with Intel? Given the choice I would rather have a Intel smart(whatever) than a cripled ARM (in comparisom). As it is now, Nokia will be late also for MeeGo, maybe too late? Intel smartphones will get there first.
The Following User Says Thank You to jsa For This Useful Post: | ||
|
2010-10-27
, 07:46
|
Banned |
Posts: 974 |
Thanked: 622 times |
Joined on Oct 2010
|
#5
|
I think you're mixing UX with the technologies the UX is done with (UX vs UX framework, the result vs the tools). I'm quite sure Nokia's real MeeGo devices will have pretty much the same UX as the Harmattan N9. Nokia isn't discouraging developers developing for that UX, they're encouraging developing for that UX with a more future proof and cross-platform tools. Just speculation, but I find it hard to believe that they'd scrap all MTF and Orbit applications they've already done. I think the plan would be to maybe migrate them to Qt Quick while already using that for new development.
What you refer to as Intel MeeGo is the vanilla MeeGo(it's the same on Intel and ARM). It's even worse on the Aava(x86 reference handset) than it is on the N900 at the moment. N900 is the only device with MeeGo where you can do a phone call at the moment.
|
2010-10-27
, 07:56
|
Posts: 196 |
Thanked: 224 times |
Joined on Sep 2010
@ Africa
|
#6
|
The N9 will run Maemo with a "MeeGo" UX. But the (Maemo)MeeGo UX will not be the UX that is going to be used on real MeeGo phones.
Nokia will not encourage people developing for that UX, but will instead encourage developing on Qt and Qt Quick.
This will probably be just fine, but think about all the wasted work: Symbian4 UX wasted, Maemo\MeeGo UX wasted. Strange indeed.
|
2010-10-27
, 11:01
|
Posts: 2,802 |
Thanked: 4,491 times |
Joined on Nov 2007
|
#7
|
As I understand, Intel MeeGo for handsets is as good as finished, ready for prime time.
The Following 2 Users Say Thank You to lma For This Useful Post: | ||
|
2010-10-27
, 15:56
|
Posts: 1,746 |
Thanked: 2,100 times |
Joined on Sep 2009
|
#8
|
It's also far from ready for prime time. MeeGo 1.1 (due to be "released" shortly) contains many bugs that would be considered release blockers in any other distribution but get through here because of MeeGo's "take what's in the repos on $RELEASEDATE and call it $NEXTVERSION" policy.
Additionally, it looks like there's going to be an ABI break with 1.2 (softfp vs hardfp) so even the promise of forward binary compatibility is broken.
In short, MeeGo Handset 1.1 is only useful for development purposes, 1.2 (hopefully) will be the first release that will be suitable for building commercial products and that's 6 months away.
The Following User Says Thank You to wmarone For This Useful Post: | ||
|
2010-10-27
, 16:26
|
Banned |
Posts: 974 |
Thanked: 622 times |
Joined on Oct 2010
|
#9
|
|
2010-10-27
, 16:35
|
Posts: 41 |
Thanked: 33 times |
Joined on Sep 2007
|
#10
|
Additionally, it looks like there's going to be an ABI break with 1.2 (softfp vs hardfp) so even the promise of forward binary compatibility is broken.
http://asia.cnet.com/reviews/mobilep...2204005,00.htm
MeeGo is the future for Nokias smartphones. At least that is the plan, but making good plans has never been a problem for Nokia, they need to execute and deliver as well.
The N9 will run Maemo with a "MeeGo" UX. But the (Maemo)MeeGo UX will not be the UX that is going to be used on real MeeGo phones. Nokia will not encourage people developing for that UX, but will instead encourage developing on Qt and Qt Quick. This will probably be just fine, but think about all the wasted work: Symbian4 UX wasted, Maemo\MeeGo UX wasted. Strange indeed.