Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

IE10: How does it really stack up?

lucidchart.com

Post reply on HN
Print view View original

41–50 of 67 posts

Re: IE10: How does it really stack up?

#41

Post by at-fates-hands »

andybak wrote: post #11
monsterix wrote: post #6

Well, let's agree that IE10 does well whatever it is designed to do well. Cool. Now what? We have an IE10 browser that compares well with Google Chrome, Opera and perhaps Firefox too (I don't know the exact details about your tests that were making Firefox crash as often as you've claimed in your article). So is this the point where Microsoft takes on the real challenge? Will it go beyond its typical high-speed sales…

IE 6, 7 and maybe 8 users are probably running XP so can't upgrade. IE 9 users on Vista are similarly out of luck. I won't be recommending IE 10 even to my clients on Windows 7 or 8 until they have an silent auto-updater and a frequent release cycle. It's the only way we'll stop IE's user base holding back the web.

This is the one thing which always mystified me about MS and IE. Why do they continually dead end their browser to a specific OS release?

I can't imagine someone in their marketing department actually thought by doing so would get people to upgrade their OS so they could have a more up to date browser.

Re: IE10: How does it really stack up?

#42

Post by btipling »

Others have already mentioned the probably slow pace of IE updates. Another thing I'll mention is that testing IE requires Windows, and I haven't worked at a place in years where anyone on my team was using Windows. Years. I've worked at Ask.com, Cloudkick, Rackspace, and now a new startup. Until I can test IE on a Mac, I wont bother to support it unless customers mention something is broken, and they rarely do. Because few use IE.

Re: IE10: How does it really stack up?

#43

Post by untog »

pbhjpbhj wrote: post #27
simonster wrote: post #9

This should really be titled "IE10: How does it really stack up in one benchmark."

Not just one benchmark, but one apparently completely undocumented benchmark run under Windows 8 on a single laptop. They don't mention how many times the benchmark ran which makes me suspicious that the answer might be one?? Unless they release the benchmarking tool then this result seems pretty worthless to me. > we’ve developed a benchmark that runs inside of the Lucidchart diagramming application // So maybe that…

So maybe that line for Firefox could as well read "Lucidchart crashed"?

No, I'd say that JS should never crash the browser, no matter what.

Re: IE10: How does it really stack up?

#44

Post by 27182818284 »

at-fates-hands wrote: post #41
andybak wrote: post #11

Earlier quoted context omitted.

IE 6, 7 and maybe 8 users are probably running XP so can't upgrade. IE 9 users on Vista are similarly out of luck. I won't be recommending IE 10 even to my clients on Windows 7 or 8 until they have an silent auto-updater and a frequent release cycle. It's the only way we'll stop IE's user base holding back the web.

This is the one thing which always mystified me about MS and IE. Why do they continually dead end their browser to a specific OS release? I can't imagine someone in their marketing department actually thought by doing so would get people to upgrade their OS so they could have a more up to date browser.

Chrome doesn't work on older versions of OS X either.

Developers don't like to develop for legacy systems.

Re: IE10: How does it really stack up?

#45

Post by vegardx »

polshaw wrote: post #37
Jabbles wrote: post #36

Earlier quoted context omitted.

Internet Explorer will start automatically updating. http://blogs.windows.com/ie/b/ie/archive/2011/12/15/ie-to-st...

The question is how often. Adopting the firefox 2/3 model (albeit less nagging a-la-chrome) is a great step forward from the IE6 one we have had up to now, but they really need to match the rapid release schedules of mozilla and google today. At a minimum quarterly updates (features/engine updates, not just security fixes) to stop hindering the web.

Less naggy? I find Firefox to be one of the most naggy browsers about upgrades. Or have they changed this recently? With Chrome you just see a notification on the settings menu, and a restart brings you up to the next version. I really hope IE adopts this model.

Re: IE10: How does it really stack up?

#46

Post by digitalinfinity »

VengefulCynic wrote: post #7

There is one more strange thing about IE10 that I should mention. IE9 often maxes out one CPU core when a Lucidchart diagram is open, even when the user is completely idle. IE10 is somewhat better, but on our test machine it still used about 50% of one core when the user is idle. No other browser has any detectable CPU load under the same conditions. Has anyone else seen behavior similar to this in their own javascri…

According to http://blogs.msdn.com/b/ie/archive/2012/06/13/advances-in-ja..., IE has separate GC and JIT threads- if I were to guess, I bet it's the GC

Re: IE10: How does it really stack up?

#48

Post by sliverstorm »

vegardx wrote: post #45
polshaw wrote: post #37

Earlier quoted context omitted.

The question is how often. Adopting the firefox 2/3 model (albeit less nagging a-la-chrome) is a great step forward from the IE6 one we have had up to now, but they really need to match the rapid release schedules of mozilla and google today. At a minimum quarterly updates (features/engine updates, not just security fixes) to stop hindering the web.

Less naggy? I find Firefox to be one of the most naggy browsers about upgrades. Or have they changed this recently? With Chrome you just see a notification on the settings menu, and a restart brings you up to the next version. I really hope IE adopts this model.

He said, "less naggy a-la chrome". Firefox nags, chrome doesn't.

Re: IE10: How does it really stack up?

#49

Post by sliverstorm »

monsterix wrote: post #6

Well, let's agree that IE10 does well whatever it is designed to do well. Cool. Now what? We have an IE10 browser that compares well with Google Chrome, Opera and perhaps Firefox too (I don't know the exact details about your tests that were making Firefox crash as often as you've claimed in your article). So is this the point where Microsoft takes on the real challenge? Will it go beyond its typical high-speed sales…

attack the more relevant problem

You know, one way to attack this problem is to make IE10 a more compelling upgrade.

Post reply on HN