crappy iPod! 33HumfHSaKlA~jG9gd
How about this, from a blog on the MSDN site by Chris Wilson:
***** I want to be clear that our intent is to build a platform that fully complies with the appropriate web standards, in particular CSS 2 ( 2.1, once itÕs been Recommended). I think we will make a lot of progress against that in IE7 through our goal of removing the worst painful bugs that make our platform difficult to use for web developers. *****
The above only applies *if you use them*. I'm not sure I agree that MS OFfice for the Mac is unsecure, but even if it is, just having it installed...
MS employees admit IE is a pain in the butt for web developers.
***** In that vein, IÕve seen a lot of comments asking if we will pbutt the Acid2 browser test published by the Web Standards Project when IE7 ships. IÕll go ahead and relieve the suspense by saying we will not pbutt this test when IE7 ships. *****
Slam dunk. He follows up with some weasel words about how it's too hard to pbutt, yet Safari has managed to do so.
***** We fully recognize that IE is behind the game today in CSS support. WeÕve dug through the Acid 2 Test and analyzed IEÕs problems with the test in some great detail, and weÕve made sure the bugs and features are on our list - however, there are some fairly large and difficult features to implement, and they will not all sort to the top of the stack in IE7. *****
Translation: IE7 is still going to be fundamentally flawed wrt CSS when it's 'done'.
Sandman wrote It's not an issue of advocacy, or performance in this case, but rather security. Microsoft has not demonstrated ANY ABILITY WHATSOEVER to construct software that is not riddled with...
-- Lefty All of God's creatures have a place.......... .........right next to the potatoes and gravy.