I like the effect of competition on Microsoft.
I'd like it much more if it made them irrelevant, or preferably bankrupt.
Give it time.
An Early Look At IE9 for Developers
41–50 of 96 posts
Re: An Early Look At IE9 for Developers
#42Border radius!
Sweet Moses yes. Rounded corners should be a setting, not a project.
Re: An Early Look At IE9 for Developers
#43Honest question: what does Microsoft stand to gain by doing all this work instead of just using WebKit?
Is it still conspiracy theory to suggest that they are the ones with the most to lose from a universally reliable JS and HTML implementation, so they should want to do enough to keep IE competitive, but not enough to make it fully compatible with everyone else?
Re: An Early Look At IE9 for Developers
#44I like the effect of competition on Microsoft.
I'd like it much more if it made them irrelevant, or preferably bankrupt.
Yes, saying bad things about Microsoft is frowned upon.
OOXML & bribes, anyone? SCO? Patent threats? Netscape? Holding back the web for 10 years? Countless other acts of evil bullshit?
I guess this is the same kind of denial that makes HN throw a hissy-fit at trying to bring up the very real problem that is Islam (in Europe).
See no evil, hear no evil.. What a wonderful community of very intelligent people we have here, heads firmly lodged in their asses. Let's never talk about anything that really matters in the world.
Re: An Early Look At IE9 for Developers
#45Earlier quoted context omitted.
Nope, Outlook now uses the Word rendering engine, since it's part of the Office family. Totally makes sense right?
That was it, thanks for the clarification. I still can't believe they're maintaining two distinct HTML renderers...
Considering the politics of such a large company, they're lucky if they only have two.
Re: An Early Look At IE9 for Developers
#46Earlier quoted context omitted.
Control and influence. Backwards compatibility. And they probably still believe they can do it better.
I'm not sure that they can't. Give Microsoft a compelling business reason to build a great browser that also supports IE 8,7, and 6 rendering modes, and I bet they'll do it.
I think part of the problem is that they don't seem to view building good products as a 'compelling business reason.'
Re: An Early Look At IE9 for Developers
#47Maybe I'm just an optimist but I'm really glad to see that MS is even looking at the Acid3 and SunSpider tests as important metrics.
Me too. Not that they have much choice. Even the non-geeks in my office have noticed that they can work faster with Firefox.
As more things move to the web, built on web standards, they can't afford to continue having the worst browser by far.
Re: An Early Look At IE9 for Developers
#48Earlier quoted context omitted.
Nope, Outlook now uses the Word rendering engine, since it's part of the Office family. Totally makes sense right?
That was it, thanks for the clarification. I still can't believe they're maintaining two distinct HTML renderers...
Describing what the Word engine does with HTML as "rendering" is probably being charitable.
Re: An Early Look At IE9 for Developers
#49Earlier quoted context omitted.
At least it's almost as fast as the slowest competitor...
Yeah, I love how they say IE is no longer an "outlier." They need to use trickery in the graph so that it's hard to tell that it's still 3x slower than Chrome or Safari.
I'm looking for the trickery, and I haven't spotted it yet. Can you elaborate?
Re: An Early Look At IE9 for Developers
#50This is nice - I don't think I've seen Microsoft look at themselves this candidly before. Next thing you know we'll have commercials saying "IE9? That was my idea!"
It'll be people dressed up in Firefox, Safari, and Chrome costumes. "One day, I had the idea that browsers should follow web standards. And guess what? 10 years later Microsoft started following them! I'm an open source web rendering engine, and IE 9 was my idea."