Re:It Doesn't Matter if it's Humiliating
on
Why Nokia Is Toast
·
· Score: 3, Insightful
S40 is not going anywhere, I don't get why some people understood otherwise? For people who want to stay on S40 dumbphones, they are going to continue putting up new ones. There was no migration path up-market even between Nokia devices, so that point is moot.
Re:It Doesn't Matter if it's Humiliating
on
Why Nokia Is Toast
·
· Score: 1
You mean there was an upgrade path between Symbian devices, beyond "migrate your data and take pains installling your favorite applications"? Oh, and these are top handsets using Opera Mini, quite a skewed metric. There are no "hundreds of millions" of users there, in fact they celebrate one hundred million total in Part 1 of the report you refer to.
Other unexplainable fact would be existence of laptop manufacturers all selling preinstalled Windows 7, yet exploring Linux for "disruptive" netbooks, tablets, and the like.
I'll rather ask myself: what more could they have done to pull Nokia out of the hole it is in? Push MeeGo on all top-end devices now? Let's see how ready it is when they release that planned device. Bite the bullet and continue flogging the dying "Qt for Symbian" horse? Right, as if the mourning Slashdotters would jump at the chance to develop applications for that.
If you don't understand just what it means for NOKIA to partner with MICROSOFT then frankly you don't belong on this site. The two are arch enemies and Nokia spend a fortune on Symbian just to get its own operating system so it wouldn't be a the beg and call of Microsoft.
Wow, that's some scary Slashdot folklore.
To Nokia up until last Friday, Microsoft was a company that supplies most of the IT software. It was certainly not a viable competitor, let alone the 'arch enemy'. You, and some other commenters here, should spend less time on fantasy roleplaying.
Um, so the only chance is to follow the fastest growing market. Too bad nobody told that to all the Linux developers who pretty much ignored any current market trends while producing some great software you are now using.
The only chance I see for Qt is a fork and a very quick community driven development of Qt for android.
You realize that software with graphical interfaces does not begin and end on smartphones, do you? And that Android is not the ultimate gift to all software developing humanity? Um, I just wasted a few minutes of my time. I should not have bothered with someone clueless enough to consider "Qt for Android" seriously.
Right, like it happened to HTC. The poor Taiwanese didn't even get a worthy mobile platform from MS, so they had to bet their success on goddamned Windows Mobile. And once they were locked in, it was near impossible to jump to a better choice (for them) when it presented itself.
Look, I'm an OSS developer, but I find this knee-jerk reaction to anything that has the word "Microsoft" in it immature. Nokia had no dick and balls to ditch Symbian in due time. Now it has finally found the balls to do so (and no wonder, look at the market share dynamics), but is short of other options. Going with Android means participating in the race to the bottom, contesting services development with Google who incidentally control your platform, and geting into yet unresolved issues with platform fragmentation. WP7 is available now, it is not technologically obsolete, and Microsoft is genuinely desperate to get some companies on board for it. Later on Nokia can choose to leave it, unless everybody's favorite conspiracy theories are right.
MeeGo... has proven to be a longer story, and some brain rinses needed to be administered on how to develop it. BTW, MeeGo is officially a Linux Foundation gig, so it can go on with or without Nokia.
I have always suspected that the "Qt for all Nokia devices" plan is not feasible anyway. Putting Qt on Symbian is like putting lipstick on a pig. And it caused a tremendous amount of drag on development of Qt. Now, hopefully, we can shed it and concentrate on relevant platforms. Such as MeeGo, which is not going anywhere yet.
Now I see Nokia is traveling down all three paths. What?
It's pretty much continuing what it was doing, except now it diverts part of the insane R&D money that used to be sunk in Symbian to little effect, towards producing some WP7 devices where it does not have to do a lot software from scratch. I mean, it's an improvement.
Why is Symbian dying? Last I checked the smartphone adoption was something like 20% at global level. Much less that that in individual countries. What are the 80% dumbphones of the world running
They are running S40 and the like. S40 and S30 is still Nokia's money-making machine, and they continue to be part of Nokia's strategy. Symbian needs to be buried.
Funny how everybody fall over each other to defend the B tag, but nobody admits that abuse of tables is indeed bad for accessibility. I think the GP comment meant primarily problems with using tables for pretty placement.
In practice, a tuple of data contained in the internal passport is currently used everywhere in Russia for identification. So this system will replace the unwieldy old way of identification for all people, and won't make much difference for identity thieves.
So, when it comes to smart pointers as data members, no alternative is entirely good. Either you get shared ownership, or you can't effortlessly copy-construct your member. For shared ownership, C++any-decade-now provides no copy-on-modify facilities (Qt does), so you have to be careful about what your objects share. shared_ptr uses atomic operations in multi-threaded programs, so if you use it just for fool-proof deallocation, you may be bumping into more memory barriers than is good for your program's performance.
Slashdot Mirror
S40 is not going anywhere, I don't get why some people understood otherwise?
For people who want to stay on S40 dumbphones, they are going to continue putting up new ones.
There was no migration path up-market even between Nokia devices, so that point is moot.
You mean there was an upgrade path between Symbian devices, beyond "migrate your data and take pains installling your favorite applications"?
Oh, and these are top handsets using Opera Mini, quite a skewed metric. There are no "hundreds of millions" of users there, in fact they celebrate one hundred million total in Part 1 of the report you refer to.
Other unexplainable fact would be existence of laptop manufacturers all selling preinstalled Windows 7, yet exploring Linux for "disruptive" netbooks, tablets, and the like.
Sorry, it's hard to read your comment seriously because of the effect depicted here:
http://www.penny-arcade.com/comic/2002/7/22/
I'll rather ask myself: what more could they have done to pull Nokia out of the hole it is in? Push MeeGo on all top-end devices now? Let's see how ready it is when they release that planned device. Bite the bullet and continue flogging the dying "Qt for Symbian" horse? Right, as if the mourning Slashdotters would jump at the chance to develop applications for that.
Many people seem to be uncapable to grasp the difference between hiring former Microsoft execs and falling under Microsoft's control.
If you don't understand just what it means for NOKIA to partner with MICROSOFT then frankly you don't belong on this site. The two are arch enemies and Nokia spend a fortune on Symbian just to get its own operating system so it wouldn't be a the beg and call of Microsoft.
Wow, that's some scary Slashdot folklore.
To Nokia up until last Friday, Microsoft was a company that supplies most of the IT software. It was certainly not a viable competitor, let alone the 'arch enemy'. You, and some other commenters here, should spend less time on fantasy roleplaying.
Um, so the only chance is to follow the fastest growing market.
Too bad nobody told that to all the Linux developers who pretty much ignored any current market trends while producing some great software you are now using.
The only chance I see for Qt is a fork and a very quick community driven development of Qt for android.
You realize that software with graphical interfaces does not begin and end on smartphones, do you? And that Android is not the ultimate gift to all software developing humanity?
Um, I just wasted a few minutes of my time. I should not have bothered with someone clueless enough to consider "Qt for Android" seriously.
Right, like it happened to HTC. The poor Taiwanese didn't even get a worthy mobile platform from MS, so they had to bet their success on goddamned Windows Mobile. And once they were locked in, it was near impossible to jump to a better choice (for them) when it presented itself.
Look, I'm an OSS developer, but I find this knee-jerk reaction to anything that has the word "Microsoft" in it immature.
Nokia had no dick and balls to ditch Symbian in due time. Now it has finally found the balls to do so (and no wonder, look at the market share dynamics), but is short of other options. Going with Android means participating in the race to the bottom, contesting services development with Google who incidentally control your platform, and geting into yet unresolved issues with platform fragmentation. WP7 is available now, it is not technologically obsolete, and Microsoft is genuinely desperate to get some companies on board for it. Later on Nokia can choose to leave it, unless everybody's favorite conspiracy theories are right.
MeeGo... has proven to be a longer story, and some brain rinses needed to be administered on how to develop it. BTW, MeeGo is officially a Linux Foundation gig, so it can go on with or without Nokia.
You did not want to wait for step 2 to become true in order to post this witty comment. This is understandable, but might be proven wrong.
I have always suspected that the "Qt for all Nokia devices" plan is not feasible anyway.
Putting Qt on Symbian is like putting lipstick on a pig. And it caused a tremendous amount of drag on development of Qt.
Now, hopefully, we can shed it and concentrate on relevant platforms. Such as MeeGo, which is not going anywhere yet.
Now I see Nokia is traveling down all three paths. What?
It's pretty much continuing what it was doing, except now it diverts part of the insane R&D money that used to be sunk in Symbian to little effect, towards producing some WP7 devices where it does not have to do a lot software from scratch. I mean, it's an improvement.
The only possible scenario for QT under Microsoft's control
Qt is not under Microsoft's control. Nokia is not under Microsoft's control to begin with.
Now, I was eagerly waiting for the successor to the N900, running MeeGo (the successor to Maemo) and then they go and cancel it!
They don't. The successor to the N900 is to be released this year.
Why is Symbian dying? Last I checked the smartphone adoption was something like 20% at global level. Much less that that in individual countries. What are the 80% dumbphones of the world running
They are running S40 and the like. S40 and S30 is still Nokia's money-making machine, and they continue to be part of Nokia's strategy.
Symbian needs to be buried.
Couple this with "lol, let's move the hq to CA" bullshit, and they're surprised the employees aren't happy?
Where did you get that from? The HQ stays in Espoo.
Funny how everybody fall over each other to defend the B tag, but nobody admits that abuse of tables is indeed bad for accessibility.
I think the GP comment meant primarily problems with using tables for pretty placement.
Can they drive the teams and call BS on half-assed engineering like Jobs?
Oh, now I understand... He went to a doctor the day they were reviewing the alarm clock implementation on iPhone.
We should really curb our emissions (of frivolous patent applications), or else.
MeeGo?
Heh, this won't help you. They own the court, and they can even bend the laws if they want it bad enough.
In practice, a tuple of data contained in the internal passport is currently used everywhere in Russia for identification. So this system will replace the unwieldy old way of identification for all people, and won't make much difference for identity thieves.
So, when it comes to smart pointers as data members, no alternative is entirely good. Either you get shared ownership, or you can't effortlessly copy-construct your member. For shared ownership, C++any-decade-now provides no copy-on-modify facilities (Qt does), so you have to be careful about what your objects share. shared_ptr uses atomic operations in multi-threaded programs, so if you use it just for fool-proof deallocation, you may be bumping into more memory barriers than is good for your program's performance.