http://blogs.msdn.com/ie/archive/2007/11/30/the-first-year-of-ie7.aspx
The comments just about sum things up nicely
Wow, what a massacre.
Wow, what a massacre.
Mozilla have already taken
Mozilla have already taken exception to some of the claims about browser security MS have made: http://www.sitepoint.com/blogs/2007/12/05/microsoft-and-mozilla-disagree-on-browser-security/
I'm sure it warmed the
I'm sure it warmed the cockles (whatever they are) of the Microsoft collective heart to see such an outpouring of love and affection.
Wow! A whole year with how many bug fixes? Or, did I miss them? Same age as Firefox 2.0 (Oct. 2006), but FF has had 11 sub-minor revisions as of Nov. 2007 for bug and security fixes.
Were I an IE developer, I'd just duck my head and slink off into the night—that, or throw a chair at Ballmer.
cheers,
gary
The Group Program manager
The Group Program manager references a report by the corporation's security director (without mentioning the fact) saying they done good and then pats his team on the back for their good work. Sheesh, is that desparation or what? Did he think no one would bother to look (or care)?
You can't help but notice that standards are slipping at Mozilla too. The last two Firefox updates have been quickly followed with a subsequent update because of stuff the first update broke. At this rate they are going to need to start treating even version numbers as betas and odd numbers as the real deal.
I had to smile at the claims
I had to smile at the claims of decreased problem reporting pointing to how well IE7 was performing and the subsequent comment to the effect that it wasn't surprising given the fact that MS had effectively closed any reporting routes and still seemingly had no bug tracking system in place.
I too am mildly concerned at Mozilla's recent activity, three or four point revisions in under 10? days does not actually bode well, people do not want to hold that up as an example of how well mozilla do compared to IE, and Mozilla need possibly to slow down and take more care?
It's true, they might be
It's true, they might be throwing out updates to issues a bit to quickly and possibly messing up other parts of the client. But what do they do when they have an issue? They fix it. So okay, they had 3 or 4 updates in 10 days, but at least they freakin update their client! :curse:
Nah Deuce. A broken update
Nah Deuce. A broken update turns people off. It makes people hold off updating until they are sure the update is really ok. Or it means people switch to another browser that isn't broken. Neither is any good.
The four updates is a red herring. There were two real updates due to security issues, the first and the third. Each of those updates managed to break some other part of the browser. In the first case undoing a previous fix. It speaks either of slack committing process or passing out committing responsibilities to people who shouldn't have it. There is no reason major open source projects shouldn't be held to the same high standards as any other piece of software. That is they did bad, they need to fix it.
Fwiw, M$ updates their client the first freakin' Tuesday of every month