Slashdot Mirror
Microsoft Previews IE9 — HTML5, SVG, Fast JS
suraj.sun sends this excerpt from CNET on Microsoft's preview of IE9 in Las Vegas just now. "At its Mix 10 conference Tuesday, Microsoft gave programmers, Web developers, and the world at large a taste of things to come with its Web browser. Specifically, Microsoft released what it's calling the Internet Explorer 9 Platform Preview, a prototype designed to show off the company's effort to improve how the browser deals with the Web as it exists today and, as important, to add support for new Web technologies that are coming right now. Coming in the new version is support for new Web standards including plug-in-free video; better performance with graphics, text, and JavaSript by taking advantage of modern computing hardware. One big change in the JavaScript engine Hachamovitch is proud of is its multicore support. As soon as a Web page is loaded, Chakra assigns a processing core to the task of compiling JavaScript in the background into fast code written in the native language of the computer's processor." Microsoft didn't say what codec they were using for the HTML5 video demo, but the Technologizer says it's H.264.
That's great and all, but Microsoft isn't competing with other browsers for market share, it's competing with its own older browsers. Anyone who knows anything about browsers is already using Firefox or Chrome or Opera, and anyone who knows nothing about browsers is using whatever came pre-installed on their computers:
IE6 if they're still on XP, Safari if they have a Mac, or IE 8 if they're running Windows 7.
Unless this is a mandatory upgrade to IE 8, it's not going to gain any ground.
And of course, the 30% of users still using IE6 will continue to do so until their computers die, or a techie relative replace it with Firefox.
It seems that even IE beat Firefox in Javascript performance now. Firefox sure has been slacking recently.
The chart you linked shows IE 9 and FF 3.7 more or less at a dead heat. So, even if this were an unfortunate turn of events, it's not as if IE 9 had a terrible lead.
But I'm not sure it's unfortunate. High performance javascript in what will likely be the world's most highly used browser for a while? Sounds pretty good to me.
Tweet, tweet.
Show the results from more than one test, and I'll be happy. As the browser showdown that was posted last week, one test doesn't prove anything. And considering the numerous open source tests that are available, why not show us all of them?
All that skepticism aside tho, if this is the truth (that IE9 will be standards based --and push the performance envelope--) then MS may be on the road to redeeming themselves... But the question remains, how tight will it be to the OS? Would a simple security flaw give a bit of JS access to the kernel? Or are they going to significantly sandbox the JS, and try to do everything right (as opposed to just the rendering)... Only time will tell if IE will become a browser friendly to geeks and developers (although something tells me it won't)...
If a man isn't willing to take some risk for his opinions, either his opinions are no good or he's no good
I had to stare at the headline for like 5 seconds before it even parsed. It just didn't seem like a reasonable configuration of words.
You've missed the overall point. This isn't even alpha quality software, it's in development. They aren't claiming they passed, they are just showing that they are making progress.
What you're doing is kinda like picking on a 2 year old for not having an expansive vocabulary.
So with all of the nifty, new stuff they are finally compliant, right? I mean no more body {text-align: center;} instead of body { margin: 0px auto; } to center a fixed width layout, right?
Those are two different things. text-align: center centers stuff in a div. the margin: 0 auto you set to a div to center that block (the div) in its container. Even IE6 works correctly with this, so I don't know what the issue is here.
For those having box-model issues with IE6, you can easily fix this by using the HTML 4.01 Strict DTD, FYI.
What good is a standard embedded video tag if there is no standard coded with which to play with it?
What good is a standard embedded image tag if there is no standard coded with which to play with it? Notice that HTML's definition of the <img> element doesn't require support for any specific image format.
PNG was developed because of patent problems with GIF. Alpha channel, 24 bit color and better compression were just extra bonuses.
Analogies don't equal equalities, they are merely somewhat analogous.
As a web developer, I'm really glad that every version of IE has been more standards compliant than the last.
It would be nice if the everyone magically installed FireFox or Safari or Chrome, but that doesn't seem to have happened yet.
Our best hope for killing off older versions of IE is newer versions of IE and an automatic upgrade path.
Frankly 8 doesn't seem that bad to me. Most of my code just works with IE 8. I'm really excited about HTML 5 and SVG in IE 9.
# (/.);;
- : float -> float -> float =
What if there was an option to not check for updates and to not load the previously loaded tabs?
It's not that they think Theora will win in the end. It's that they want some free standard to win in the end, and they know that won't happen if they (of all people) fold on H.264.
The money they'd have to pay for including it in their distribution isn't the issue. It's the fees people in future would have to pay for creating and distributing movies. They want the Web to be democratic, and that means everyone gets to contribute, whatever their financial means.
Or people who feel strongly about it will continue to use open formats and petition against software patents.
Good luck with that.
8 years ago, I've bought into Vorbis hype (coincidentally, it was about the time when I switched to Linux as primary desktop OS). My music collection was 100% Vorbis. I only bought players that could play it (e.g. iRiver).
Fast forward to today... only about 10% of my music is still in Vorbis, and I still have trouble with that (e.g. my car won't play it, so I have to recode). I'm afraid that MP3 has won, and AAC is picking up from there.
And that was with Vorbis, which was actually technically better than MP3 in many aspects (better compression, extensible meta-information with proper Unicode support etc). And Theora is technically inferior to H.264...
Still, good luck.
Let me rephrase then.
What is the better default behavior given that there is an option to alter said behavior if you don't like it?
The default behavior attempts to keep Firefox as up to date as possible. It also tries to recover from the browser crashing or some other misfortune. If I need to go in a hurry, I can close the browser and it will reopen where I left off.
Your argument seems to be that people are imbeciles if they don't have the same priorities you do. I don't subscribe to that point of view.