Developers complain that IE10 for Windows 7 was long overdue

Following browser's release, developers chide Microsoft for 'holding back the Internet' and ask, 'Where's WebGL support?'

Page 2 of 2

Mauceri said IE10 on Windows 7 improves performance with faster page loading, faster interactivity, and faster JavaScript performance; it also reduces CPU usage and improves battery life on mobile PCs.

The browser boost hardware acceleration performance of SVG and HTML4 constructs, he said. Additionally, improved drawing performance enables faster rendering patterns. The brower also yields improvements to the Chakra JavaScript engine, including profile-based, type-specialized JIT machine code, faster floating point operations, and faster object and property access.

IE10 comes with DNT (Do Not Track) signal turned on by default. It offers integrated spell checking and auto-correct, along with a retuned tabs bar to speed up the process of closing multiple tabs.

Responses to Microsoft's announcement were mixed, with much of the criticism focused on how long it took for the company to deliver IE10 to Windows 7. "Over a year ago, when you started showing IE10, I was excited. But now, you are way behind, again," wrote MSDN user RobCannon. "Why did it take so long to deliver this? Waiting for this release is literally holding back the Internet as too many people are still using older versions of IE. If Microsoft truly wanted to advance the Web, this would have been released months ago. I used to be a Microsoft fan, but you guys are making it too hard."

A couple of users called on Microsoft to support WebGL, which has earned a reputation for being potentially insecure. "Why not have an opt-in?" asked user dd26. "If you really think these are vulnerabilities, why not give the user the option to take on that risk if it indeed exists? ... When it comes to networking, nothing under the sun, alas, is fully secure."

Finally, user MgSm88 provided a laundry list of desired features for improving IE's developer tools:

  • Source map support
  • Better way to explore objects in the JS console. (See how Chrome has collapsible nodes and can handle nested objects.)
  • Better way to log objects. (See how Chrome's console.log() behaves, it allows you to explore the object, printing "[object Object]" is entirely useless.)
  • Better JS console user interface (I hate the behavior of it. Why is there a single line and multi-line mode? It should just work. I don't want to think about how I'm supposed to use it. Horrible UX design.)
  • Thinner header (3 lines of stuff before you get to the content of the debug tools?)
  • Ability to break on DOM modification of specific elements (a la Chrome).
  • "Refresh page to see messages that may have occurred"/Start capturing network traffic. Why does this all need to be explicit? I should just turn on Developer Mode in some setting somewhere and it should capture/log all this by default.
  • Ability to see applied vs. defined styles and how styles are overriding each other.

I also wish you guys would move to a more frequent release schedule with more incremental updates. If every other tech company can be agile with their browser releases, why can't MS? Just have milestones with long-term support, like Firefox has adopted, and you can make corporate customers happy while not hampering innovation.

This story, "Developers complain that IE10 for Windows 7 was long overdue," was originally published at Get the first word on what the important tech news really means with the InfoWorld Tech Watch blog. For the latest developments in business technology news, follow on Twitter.

| 1 2 Page 2