Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mango will bring WP7 on par with or higher than iOS and Android in just about all regards.
 
Last edited:
To be honest, I was baffled why they didn't provide that level of functionality to start with. I mean the competition already had this feature and its not new feature.
 
To be honest, I was baffled why they didn't provide that level of functionality to start with. I mean the competition already had this feature and its not new feature.

They had to start somewhere, iOS was missing a lot when it first came out, remember how you couldn't copy and paste, use MMS, and a lot of other things. They probably left it out, because it's better to add features over time than have a bunch of features that only half work.
 
They had to start somewhere, iOS was missing a lot when it first came out, remember how you couldn't copy and paste, use MMS, and a lot of other things. They probably left it out, because it's better to add features over time than have a bunch of features that only half work.

True, but the iPhone was the first of its kind. WebOS, android both had multitasking from the get go. If you remember, it was apple's stance that you don't need multitasking as the main reason why it wasn't there. Even now, iOS doesn't have true multitasking, at least not like the other OS's
 
Interesting to see that the Nexus S manages 11fps on the html 5 test without any hardware acceleration. Hopefully Google will add it to Ice Cream Sandwich later this year.

Still, IE9 looks smooth as silk in Mango. Really good stuff from MS.
 
Last edited:
True, but the iPhone was the first of its kind. WebOS, android both had multitasking from the get go. If you remember, it was apple's stance that you don't need multitasking as the main reason why it wasn't there. Even now, iOS doesn't have true multitasking, at least not like the other OS's

MMS should of been there day one along with basic multitasking.
No, because they were made by Microsoft to obviously prop themselves up. :rolleyes:

The fact they are hosted on microsoft.com should have been a nice clue.

While true I have looked threw the code of the test page and I see nothing and I mean nothing that should effect any browser you run on but it is just basic code. Just from what I can tell IE hows better hardware acceleration than safari. Safari lags in a lot of things.

you should check out some stuff from Google IO were Google had Chrome doing some really cook things with the fish demo from MS sit. It was doing better than IE9 was with more fish. I think it was somethings that is not fully released yet but was showing that it was there and that to me tells me another reason that MS is not cheating just they added in more features to IE at the time.

Whilst I am looking forward to Mango.

I have both a HTC Trophy Win 7 and an iPhone 4...




I am however extremely skeptical over the 'speed reading' test.


Safari on my Octo core mac gets the same 2fps

http://ie.microsoft.com/testdrive/Performance/SpeedReading/Default.html

and so does Chrome..... exactly 2 fps ?


I think this is an artificial test.

I am pulling 15 FPS off my computer on Chrome.
 
Such is mango...
 

Attachments

  • winmango.jpg
    winmango.jpg
    45.4 KB · Views: 115
While true I have looked threw the code of the test page and I see nothing and I mean nothing that should effect any browser you run on but it is just basic code. Just from what I can tell IE hows better hardware acceleration than safari. Safari lags in a lot of things.

You're looking for "if(IE)" stuff, that's not what I meant. HMTL5 is very large. Very, very, very large. If Microsoft spends some time over-optimizing a very little subset of it on their stuff, a small subset no one else concentrates on, and then writes test case for that, of course they are going to come out on top.

There are plenty of ways vendors can write biased benchmarks. Not all of these require "trickery". Then you get users saying "WP7 destroys in HHTML5 benchmarks!" when the truth is "WP7 destroyed in tests made to show only the good sides of the HTML5 implementation on WP7 while ignoring other test cases where the competition scores better!".
 
You're looking for "if(IE)" stuff, that's not what I meant. HMTL5 is very large. Very, very, very large. If Microsoft spends some time over-optimizing a very little subset of it on their stuff, a small subset no one else concentrates on, and then writes test case for that, of course they are going to come out on top.

There are plenty of ways vendors can write biased benchmarks. Not all of these require "trickery". Then you get users saying "WP7 destroys in HHTML5 benchmarks!" when the truth is "WP7 destroyed in tests made to show only the good sides of the HTML5 implementation on WP7 while ignoring other test cases where the competition scores better!".

Perhaps but safari's performance has never been all that stellar so why go to all that trouble to show off a test that could possible be easily refuted, especially when safari is slower anyways. Doesn't provide a good risk vs. reward ratio
 
Perhaps but safari's performance has never been all that stellar so why go to all that trouble to show off a test that could possible be easily refuted, especially when safari is slower anyways. Doesn't provide a good risk vs. reward ratio

How can it be refuted ? Those MS tests were discussed at length on Slashdot. They test a small subset where IE happens to perform well. That's all there is to it, there's no refuting to do. IE does do well on those particular test cases, which is why MS cherry picked them.

However, those few test cases are not indicative of support/performance of HTML5 rendering in general.

How hard is this to grasp guys, come on...
 
How can it be refuted ? Those MS tests were discussed at length on Slashdot. They test a small subset where IE happens to perform well. That's all there is to it, there's no refuting to do. IE does do well on those particular test cases, which is why MS cherry picked them.

However, those few test cases are not indicative of support/performance of HTML5 rendering in general.

How hard is this to grasp guys, come on...

What this really highlights is that HTML5 is still a very, very long way from being even remotely suitable for replacing Flash on the web. Flash remains as one of the only ways for developers to ensure that content appears consistently across all browsers and platforms.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.