I wrote a little while ago about how Chrome was not as Enterprise "friendly" as Internet Explorer was due to the number and nature of the configuration options supported by latter versions of Internet Explorer (IE). You can read more about how IE allows for great control of the user experience and security settings here:
http://aokcompat.blogspot.com/2011/03/ie-vs-chrome-drawing-enterprise.html
Well, it appears that the other player in the market (I am being a little unfair here) has introduced their own "failure plan" for the Enterprise; Rapid updates from Mozilla. Firefox is now planning Firefox 7 in six weeks and the Firefox 8 six weeks after that... With a planned follow-up of a major update every six weeks after that. Whoa! You can read the Twitter update here: http://twitter.com/#!/asadotzler/status/83411876855291905
While consumers generally don't mind updating their applications every few weeks or months (Hey, it seems like every time I turn on my iPad, have at least 6 updates) the Enterprise release cycle is much slower. Think years instead of months.
Some organizations only allow a build update every 6-months with a major revision every 18 months. With Mozilla now planning a new update/release every 6 weeks, I just can't see how enterprise testing teams much less the deployment teams could catch-up.
Even some of the Mozilla team share this thinking as Mike Kaply comments;
Mike get's the Enterprise browser space - and, you can tell from some of the comments from other Mozilla developers on his posting, that he is more "alone" that I had hoped.
You can read more here:
http://mike.kaply.com/2011/06/23/understanding-the-corporate-impact/#comment-10494
http://aokcompat.blogspot.com/2011/03/ie-vs-chrome-drawing-enterprise.html
Well, it appears that the other player in the market (I am being a little unfair here) has introduced their own "failure plan" for the Enterprise; Rapid updates from Mozilla. Firefox is now planning Firefox 7 in six weeks and the Firefox 8 six weeks after that... With a planned follow-up of a major update every six weeks after that. Whoa! You can read the Twitter update here: http://twitter.com/#!/asadotzler/status/83411876855291905
While consumers generally don't mind updating their applications every few weeks or months (Hey, it seems like every time I turn on my iPad, have at least 6 updates) the Enterprise release cycle is much slower. Think years instead of months.
Some organizations only allow a build update every 6-months with a major revision every 18 months. With Mozilla now planning a new update/release every 6 weeks, I just can't see how enterprise testing teams much less the deployment teams could catch-up.
Even some of the Mozilla team share this thinking as Mike Kaply comments;
As person involved in the corporate deployment of Firefox, I think it’s a really bad idea. Companies simply can’t turn around major browser updates in six weeks (and each one of these is a major update). With security releases, there was a reasonable expectation that web applications wouldn’t break as a result of changes. With these releases, there is no such expectation. So a full test cycle needs to be run with every release. By the time this cycle is completed and the browser is piloted and deployed, another version of Firefox would already be released so they’d already be behind. And in the mean time, all of their browsers will be insecure, because all security updates are rolled into the major versions.You can read his whole post here: http://mike.kaply.com/2011/06/21/firefox-rapid-release-process/
Mike get's the Enterprise browser space - and, you can tell from some of the comments from other Mozilla developers on his posting, that he is more "alone" that I had hoped.
You can read more here:
http://mike.kaply.com/2011/06/23/understanding-the-corporate-impact/#comment-10494
No comments:
Post a Comment