Slashdot Mirror
Auto Install of IE 7 Delayed In Japan
filenavigator writes "Microsoft has delayed the automatic install of IE 7 in Japan. There's an an interesting response in one of the MSDN blogs. IT pros are saying that they have done this because business users asked it to be delayed. It seems to me many business users here in North America wanted it to be delayed as well, but were forced to scramble and deploy IE 7 blocking software. This looks like more proof that the IE 7 automatic push was more for marketing reasons, than security. If it were a security issue, than why wait on the Japanese push?" Does anyone know the 'technical' reason that the autoinstall was delayed?
Answer: No I don't!
Disclaimer: I do not know what I am talking about.
Its kind of funny. Usualy we hear about how its the developer's fault that they are writting "non-standard compliant" code, and that they deserve what they get if it breaks in Firefox, or whatever... Now though, since code break because the code isn't standard compliant enough (while IE7 isn't very good still, it does a much better job rendering standard CSS than it does randering IE6 targetted crap) in a microsoft browser, its Microsoft thats evil :)
A lot of the software that are breaking which are not related to web, however, do so because of their use of the MSHTML rendering engine... In a -lot- of cases, just changing the doctype tend to make things -relatively- OK. For the rest...well, IE7 has been in beta and RC for how long now? I know that IT stuff doesn't happen overnight, but Microsoft gave as much warning as they possibly could. If stuff broke (and I'm guilty of that, some web apps I wrote did break, and I didn't take time to test it in IE7), its the developer's own damn fault. They had like a year or something. Jesus...