No, it's just as easy to have poor performing HTML5. Conversely look at Mark Ecko's website, or AgencyNet or Dave Werner...these are well-written Flash sites that have minimal CPU usage and run smooth even on my old N900.
Of course an open standard is better, but that's the HTML5 argument, not performance.
If only that had some planb document that discussed there plans and addressed those issues~
If only they said why this plan is financially better. They talk of actions that have HUGE expenditure but don't say anything about costs or profit and obviously don't compare in those terms to the MS deal. This will fail because they are appealing to shareholders - people who care about financials - with no financial details.
It's highly doubtful they have that much otherwise they would have already pulled this off rather than blustering.
Particularly since they don't seem to have a plan for doing this, i mean that 'Plan B' calls for an end to outsourcing in favour of in-house development, obviously this is preferrable but that is going to be HUGELY expensive.
Also they want to install a new CEO with specific qualities...they don't say who this could be and fire many members of the management team. So of course they are going to have to pay out Elop and the other members of the management team.
They want to offer higher salaries to attract more 'talent', again not a bad thing but very expensive.
They want to invest more heavily in MeeGo which is a long way off being finished, so thats yet another expensive proposition.
In short they are appealing to the shareholders - those who care about the financials - with a plan that will have a MASSIVE effect on the financial situation, yet they don't give any actual numbers. My bet is Elop and the BoD have some pretty convincing numbers supporting their plan.
The CEO of Nokia, who spearheaded this move to MS, is an ex-MS exec. Given the immediate share drop after the announcement, and the previous share growth, likely based on the possibilities of a partnership with Google, is grounds for an investigation.
1. lagging in features "multitasking, cut and paste, and custom ring tones."
those have been announced at MWC yesterday.
2. Small library of applications. Heck I bet WebOS still has more.
Well it's an infant platform, an extensive library of applications doesn't come overnight. WebOS has been out for more than 18months and the app catalog is less than 7000, WP7 has been out for less than a 3rd of that time and already surpassed 8000.
Mobile Office? Do you really think you will use office on your phone?
It's not so much about producing content from scratch but being able to view, edit and sync everything so easily.
For me the lack of good gmail integration is a big loss
What's the problem you have with it?
Thing is people are pretending that this is Microsoft's first OS in the Mobile space. It isn't called WP7 for nothing folks.
Well it's their first attempt at this market, i mean WinMo is nearly a decade old, it was never meant to compete in the current market which is vastly different.
They are making money. About a billion a quarter in net profit.
I think he meant in terms of their profit decline. Cheap chinese dumbphones are a dime a dozen these days so selling to the lowend is getting less and less profitable.
I don't see why Nokia has to only produce 'Smart' phones with a MS OS running on them. There is still a very large percentage of people that are NOT using a smart phone and have no reason to buy a smart phone when their current phone dies.
They aren't going to produce *only* smartphones, it's just that their smartphones will *only* use WP7 - except for that MeeGo device (if it is indeed a phone). Symbian is only being discontinued from smartphones, where quite frankly it's awful anyway.
Even better, how about a lightweight browser that doesn't require plugins to view videos?
How about magic?
Re:A Microsoft Nokia bad-analogy award
on
Why Nokia Is Toast
·
· Score: 1
Fair enough, i respect that you've not taken the issue personally. I was really just trying to convey the difference between RRD - considering we were discussing R&D i wasn't quite sure whether he was still referencing that with a typo - and RROD and used YLOD as an example because it is also a 'Of Death' fault.
That used two separate exploits, one in the PDF handler and the other in the OS itself.
Neither were Safari.
That PDF handler is a part of safari as it is used within safari, it isn't an external program.
It's pretty hilarious to see you guys trot out a once in a lifetime meeting of two exploits, when there were years with daily IE exploits
That's not the point at all, the point is just because an exploit exists in a desktop version of the software doesn't mean the mobile version will have the same vulnerabilities and vice-versa. That's the only point im making here. No 'this platform vs that platform' or anything like that, i have a WP7 phone and an ipad so i'm not biased one way or the other.
errr...why are you replying to me? I was illustrating the point that just because an exploit is in the mobile browser doesn't mean it's in the desktop version and vice-versa, this is regardless of whether it's an MS, Apple or FOSS platform.
Even the worst Safari exploit is just going to get into your user account.
Surely you haven't forgotten the exploit that enabled iphone OS to be jailbroken from the web browser? Security exploits don't come much worse than that.
I love how you mention Zune as a great success story... The Zune has been Microsoft's second biggest failure to date (next to the Kin, which was a preview to WP7).
You're thinking of the Zune player, he means Zune as in the Zune platform.
Unfortunately for Microsoft, WP7 has Zune written all over it--same ideas, same marketing, same distribution, etc.
Really? I don't see much similarity in their ideas, marketing and distribution to the Zune player.
And yes, that is serious fragmentation because what I didn't note was that of that 89%, 31.4% are running Android 2.0, or Android 2.1, which came out well over a year ago. A tenth of the platform is using Android 1.5 or 1.6. Roughly a third is using Android 2.0 or 2.1. About half is using Android 2.2. Less than a hundredth is using Android 2.3.
Well there is no such thing as WM7...but of course WP7 hasn't been 'losing out', it's only been out for a couple of months.
The idea that Android has to look out for Windows Phone is the same idea as MS fanboys had with every previous iteration of MS CE/Mobile and got knows what other names they have used to hide the fact of old vinegar in crappy bags.
Sounds like you haven't even used a WP7 phone.
Re:A Microsoft Nokia bad-analogy award
on
Why Nokia Is Toast
·
· Score: 1
Stop mentioning the RROD, and the YLOD on the same breath, they are totally different things.
Relax, they're both hardware failures caused by design faults, that's enough of a similarity to use it to confirm that RRD did indeed mean RROD. In no way did I say they were exactly the same thing nor did I infer that they occur at the same frequency.
I am not a sony fanboi, i have all three consoles. But to put the RROD and the so called YLOD on the same phrase is disingenious.
You mean disingenuous? If so then no it isn't, as I stated above, I didn't try to say they were exactly the same thing.
Re:A Microsoft Nokia bad-analogy award
on
Why Nokia Is Toast
·
· Score: 1
A quarter billion dollar loss for Kin is not a rounding error.
Slashdot Mirror
Each to their own, i guess it's a matter of preference.
Flash is a performance nightmare
No, it's just as easy to have poor performing HTML5. Conversely look at Mark Ecko's website, or AgencyNet or Dave Werner...these are well-written Flash sites that have minimal CPU usage and run smooth even on my old N900.
Of course an open standard is better, but that's the HTML5 argument, not performance.
If only that had some planb document that discussed there plans and addressed those issues~
If only they said why this plan is financially better. They talk of actions that have HUGE expenditure but don't say anything about costs or profit and obviously don't compare in those terms to the MS deal. This will fail because they are appealing to shareholders - people who care about financials - with no financial details.
It's highly doubtful they have that much otherwise they would have already pulled this off rather than blustering.
Particularly since they don't seem to have a plan for doing this, i mean that 'Plan B' calls for an end to outsourcing in favour of in-house development, obviously this is preferrable but that is going to be HUGELY expensive.
Also they want to install a new CEO with specific qualities...they don't say who this could be and fire many members of the management team. So of course they are going to have to pay out Elop and the other members of the management team.
They want to offer higher salaries to attract more 'talent', again not a bad thing but very expensive.
They want to invest more heavily in MeeGo which is a long way off being finished, so thats yet another expensive proposition.
In short they are appealing to the shareholders - those who care about the financials - with a plan that will have a MASSIVE effect on the financial situation, yet they don't give any actual numbers. My bet is Elop and the BoD have some pretty convincing numbers supporting their plan.
The CEO of Nokia, who spearheaded this move to MS, is an ex-MS exec. Given the immediate share drop after the announcement, and the previous share growth, likely based on the possibilities of a partnership with Google, is grounds for an investigation.
He already addressed that potential issue.
1. lagging in features "multitasking, cut and paste, and custom ring tones."
those have been announced at MWC yesterday.
2. Small library of applications. Heck I bet WebOS still has more.
Well it's an infant platform, an extensive library of applications doesn't come overnight. WebOS has been out for more than 18months and the app catalog is less than 7000, WP7 has been out for less than a 3rd of that time and already surpassed 8000.
Mobile Office? Do you really think you will use office on your phone?
It's not so much about producing content from scratch but being able to view, edit and sync everything so easily.
For me the lack of good gmail integration is a big loss
What's the problem you have with it?
Thing is people are pretending that this is Microsoft's first OS in the Mobile space. It isn't called WP7 for nothing folks.
Well it's their first attempt at this market, i mean WinMo is nearly a decade old, it was never meant to compete in the current market which is vastly different.
They are making money. About a billion a quarter in net profit.
I think he meant in terms of their profit decline. Cheap chinese dumbphones are a dime a dozen these days so selling to the lowend is getting less and less profitable.
They still outsell ALL Android phones and Apple phones COMBINED.
But this deal affects *smartphones* which is where Nokia lags behind.
I don't see why Nokia has to only produce 'Smart' phones with a MS OS running on them. There is still a very large percentage of people that are NOT using a smart phone and have no reason to buy a smart phone when their current phone dies.
They aren't going to produce *only* smartphones, it's just that their smartphones will *only* use WP7 - except for that MeeGo device (if it is indeed a phone). Symbian is only being discontinued from smartphones, where quite frankly it's awful anyway.
This is what happens when people try to replace emacs.
But i *need* tetris in my text-editor.
Even better, how about a lightweight browser that doesn't require plugins to view videos?
How about magic?
Fair enough, i respect that you've not taken the issue personally. I was really just trying to convey the difference between RRD - considering we were discussing R&D i wasn't quite sure whether he was still referencing that with a typo - and RROD and used YLOD as an example because it is also a 'Of Death' fault.
or was a female and meant what she wrote.
That used two separate exploits, one in the PDF handler and the other in the OS itself.
Neither were Safari.
That PDF handler is a part of safari as it is used within safari, it isn't an external program.
It's pretty hilarious to see you guys trot out a once in a lifetime meeting of two exploits, when there were years with daily IE exploits
That's not the point at all, the point is just because an exploit exists in a desktop version of the software doesn't mean the mobile version will have the same vulnerabilities and vice-versa. That's the only point im making here. No 'this platform vs that platform' or anything like that, i have a WP7 phone and an ipad so i'm not biased one way or the other.
errr...why are you replying to me? I was illustrating the point that just because an exploit is in the mobile browser doesn't mean it's in the desktop version and vice-versa, this is regardless of whether it's an MS, Apple or FOSS platform.
Even the worst Safari exploit is just going to get into your user account.
Surely you haven't forgotten the exploit that enabled iphone OS to be jailbroken from the web browser? Security exploits don't come much worse than that.
who needs something fancy like an EMP device? One word: Strategically dropped meteors.
Strategically unplugged network cables?
The big red button does it all.
No! Don't click the big red button - it's a trap! You'll be Rick Rolled!!
That's what they want you to think.
WP7 has a great solution for avoiding "page after page of little icons": a piss-poor selection of apps to download ;)
Lucky i've got a whole page of iFart clones on my iphone.
I love how you mention Zune as a great success story... The Zune has been Microsoft's second biggest failure to date (next to the Kin, which was a preview to WP7).
You're thinking of the Zune player, he means Zune as in the Zune platform.
Unfortunately for Microsoft, WP7 has Zune written all over it--same ideas, same marketing, same distribution, etc.
Really? I don't see much similarity in their ideas, marketing and distribution to the Zune player.
the problem here is that IE9 still is significantly subpar compared to mobile webkit.
How so?
I am not going to optimize any site for WP7 and its shoddy browser
Specifically what is 'shoddy'?
And yes, that is serious fragmentation because what I didn't note was that of that 89%, 31.4% are running Android 2.0, or Android 2.1, which came out well over a year ago. A tenth of the platform is using Android 1.5 or 1.6. Roughly a third is using Android 2.0 or 2.1. About half is using Android 2.2. Less than a hundredth is using Android 2.3.
Oh no, iOS has serious fragmentation too:
4.2.1: 52.89 %
4.1: 27.50 %
3.1.3: 6.43 %
4.0.2: 3.36 %
4.0.1: 2.95 %
4.0: 2.94 %
3.1.2: 2.52 %
3.2.2: 0.49 %
3.0: 0.22 %
3.1: 0.21 %
3.0.1: 0.10 %
3.2: 0.10 %
3.1.1: 0.10 %
4.2: 0.09 %
3.2.1: 0.07 %
2.2.1: 0.02 %
2.2: 0.00 %
From here
Seriously, targeting multiple OS versions and hardware configurations has been normal through the life of the desktop PC, this is not new.
Same as WM7 has been loosing out.
Well there is no such thing as WM7...but of course WP7 hasn't been 'losing out', it's only been out for a couple of months.
The idea that Android has to look out for Windows Phone is the same idea as MS fanboys had with every previous iteration of MS CE/Mobile and got knows what other names they have used to hide the fact of old vinegar in crappy bags.
Sounds like you haven't even used a WP7 phone.
Stop mentioning the RROD, and the YLOD on the same breath, they are totally different things.
Relax, they're both hardware failures caused by design faults, that's enough of a similarity to use it to confirm that RRD did indeed mean RROD. In no way did I say they were exactly the same thing nor did I infer that they occur at the same frequency.
I am not a sony fanboi, i have all three consoles. But to put the RROD and the so called YLOD on the same phrase is disingenious.
You mean disingenuous? If so then no it isn't, as I stated above, I didn't try to say they were exactly the same thing.
A quarter billion dollar loss for Kin is not a rounding error.