Active Topics
-
Firefox with Leste (5)
to Maemo 7 / Leste by teroyk - 3 days, 22 hrs ago -
Handbook (2)
to Maemo 7 / Leste by teroyk - 4 days, 21 hrs ago - more...
 |
|
2010-10-27
, 05:01
|
|
Posts: 4,384 |
Thanked: 5,524 times |
Joined on Jul 2007
@ ˙ǝɹǝɥʍou
|
#2
|
He is, isn't he?
But I thought FOSS is also partially about sticking it to da man?
But I thought FOSS is also partially about sticking it to da man?
__________________
Class .. : Power User
Humor .. : [#####-----] | Alignment: Pragmatist
Patience : [###-------] | Weapon(s): Galaxy Note + BB Bold Touch 9900
Agro ... : [###-------] | Relic(s) : iPhone 4S, Atrix, Milestone, N900, N800, N95, HTC G1, Treos, Zauri, BB 9000, BB 9700, etc
Class .. : Power User
Humor .. : [#####-----] | Alignment: Pragmatist
Patience : [###-------] | Weapon(s): Galaxy Note + BB Bold Touch 9900
Agro ... : [###-------] | Relic(s) : iPhone 4S, Atrix, Milestone, N900, N800, N95, HTC G1, Treos, Zauri, BB 9000, BB 9700, etc
Follow the MeeGo Coding Competition!
|
|
2010-10-27
, 05:27
|
|
Banned |
Posts: 974 |
Thanked: 622 times |
Joined on Oct 2010
|
#3
|
Originally Posted by ysss
Symbian will still be around, and I can't shake off the feeling that Nokias plans here are made in a sphere of "world domination" instad of simply planning to make excellent smartphones.
He is, isn't he?
But I thought FOSS is also partially about sticking it to da man?
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.
|
|
2010-10-27
, 07:13
|
|
Posts: 289 |
Thanked: 560 times |
Joined on May 2009
@ Tampere, Finland
|
#4
|
Originally Posted by ericsson
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.
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.
Originally Posted by ericsson
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.
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
|
Originally Posted by jsa
You are probably right. But I think a big error Nokia does all the time is communication. They never communicate clearly. It is a mix of plans and hopes and pure speculations, and when the time comes to deliver, they change and say; "What we really meant, and has meant all along, is .... " To be obscure is OK if you actually deliver and is succesful, but being obscure and never deliver as promised is a very very bad sign, the sign of no control. This is happening again and again with Nokia.
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.
So it is a change of direction, why should we believe it, and why shouldn,t we believe that what they actually mean this time is something different?
Maybe the US bloggers have been correct all along. Maybe Nokia doesn't have what it takes anymore?
|
|
2010-10-27
, 07:56
|
|
Posts: 196 |
Thanked: 224 times |
Joined on Sep 2010
@ Africa
|
#6
|
Originally Posted by ericsson
This isn't from the article though ...
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.
The work before Qt was wasted. The switch to Qt on Symbian and Meego means less waste in future, but highlights the waste of different toolkits before Qt.
The more interesting part of the article is 400 Microsoft engineers developing on Qt for Office on Symbian. Will Office come to Meego too then? What does that mean for FreOffice?
|
|
2010-10-27
, 11:01
|
|
Posts: 2,802 |
Thanked: 4,491 times |
Joined on Nov 2007
|
#7
|
Originally Posted by ericsson
There's no "Intel" MeeGo as such. MeeGo is developed under the Linux Foundation umbrella, with the contribution of many Intel and Nokia (but not only) engineers.
As I understand, Intel MeeGo for handsets is as good as finished, ready for prime time.
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 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
|
Originally Posted by lma
That's some awesome fearmongering there. The bug quoted in the article was highlighted and confirmed as a blocker, then resolved before 1.1, so that article is full of crap and whoever wrote it obviously doesn't care enough to fix it. Worse yet, the "read more" link goes to an ENTIRELY DIFFERENT BUG.
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
|
Originally Posted by buchanmilne
No it's from this article, but it is also discussed here in other threads.
This isn't from the article though ...
http://www.allaboutsymbian.com/featu...mbian_plat.php
|
|
2010-10-27
, 16:35
|
|
Posts: 41 |
Thanked: 33 times |
Joined on Sep 2007
|
#10
|
Originally Posted by lma
*facepalm*
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.
I'm having this major deja vu all over again. Flashbacks to OpenZaurus / OpenEmbedded included.
So much for people learning from history.
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.