5 ms·
This article is right. Firefox (and Chrome) updates should be seen in the same way as virus definition updates - something that can indeed cause chaos [1][2][3
by nl 15y ago
This article is right.
Firefox (and Chrome) updates should be seen in the same way as virus definition updates - something that can indeed cause chaos [1][2][3], but is too useful and sensible to do any other way. Similarly to virus definition updates, typically these updates don't get tested before being rolled out.
[1] http://arstechnica.com/software/news/2010/03/bitdefender-update-breaks-64-bit-windows-pcs.ars http://arstechnica.com/software/news/2010/03/bitdefender-upd...
[2] http://www.techgeekandmore.com/tag/ca-anti-virus-update-breaks-windows/ http://www.techgeekandmore.com/tag/ca-anti-virus-update-brea...
[3] http://simonedwards.blogspot.com/2010/04/mcafee-anti-virus-update-breaks-pcs.html http://simonedwards.blogspot.com/2010/04/mcafee-anti-virus-u...
- kenjackson 15y agoThere are a few big differences between virus def updates and browser updates: 1) virus def updates rarely cause any problems whatsoever. Whereas browser updates are actually just the opposite. At enterprises its not uncommon that even dot releases break some apps. So those apps need to get fixed, before wide rollout. 2) Virus def updates, when they do break people, break a LOT of people very visibly. That is, if you wait a day on a virus def update, you can pretty quickly see if it broke ppl just by doing an online search. Whereas with browser updates, its a lot more difficult to tell if any of your apps will be broken with a given update. 3) Virus def updates are often fixing issues that have the potential to directly effect your business. Whereas, except for security fixes in browsers, browser updates won't have any effect on the business. It's rare that you have an app waiting to be deployed, but you're waiting on the next version of FF for a new feature or bug fix. IOW, you're taking risk, with no upside. It's really just not the same thing at all.
- nl 15y agoAt enterprises its not uncommon that even dot releases break some apps. In my experience (nearly 15 years in enterprise development) this isn't the case at all. It used to be the case, especially with apps that used plugins or Java (both of which were common in the early 2000s), but for the most part these apps have gone now. I think it is very, very unlikely that any non-client-Java webapp that runs in Firefox 3.x will break in any significant way in any future release.
- ChRoss 15y agoSometime it's not significant break, but some little difference may cause many support calls logged, depends on the organization size. And I believe many organization are still using legacy system.
- PakG1 15y agoI work at a big tech MNC right now. We have apps that still require IE6. These are global apps. This company is also lauded for some amazing tech. Sometimes it's just difficult to allocate the necessary resources to update an app, and sometimes it's not worth it. In other cases, all the people who made the app just moved on and there's insufficient documentation to know how the app works. The code analysis process alone would be atrocious, and companies prefer to put pressure on revenue-generating initiatives, not maintenance initiatives, because if it ain't broke, don't fix it. And this is why all our computers still have IE6 installed.... @@ Fortunately, I've also got Chrome and Firefox on here because I have admin rights. edit: Given how long mainframes have been around, is it really that much of a stretch to say that these kind of legacy web apps could still be around for a few years yet, if they're really integrated deep into an organization's processes?
- nl 15y agoWe have apps that still require IE6 Yep. Hence my comment "I think it is very, very unlikely that any non-client-Java webapp that runs in Firefox 3.x will break in any significant way in any future release" IE6-only (and IE-only) exist in the enterprise. That doesn't really impact on the Firefox upgrade strategy, since people don't use Firefox to access them. (Also, MS is slowly dropping support for operating systems supporting IE6. Enterprises are very reluctant to use unsupported operating systems.)
- ZeroGravitas 15y agoDidn't all that untouchable but still working mainframe stuff at some point get stuck in an emulated window, or screen-scraped into a web app, rather than have everyone stuck on terminals forever? It would be pretty ironic, but thanks to HTML probably not that hard, to be screen scraping an IE only web app to make it available to other web browsers.
- DrPizza 15y agoOn the other hand, bad virus updates have a habit of purging critical system files, leaving machines unbootable. They have the power to be extraordinarily destructive; good luck getting a browser to do that.
- kenjackson 15y agoIndeed def updates can do that (and have). I wouldn't say they have a habit of it though. I've done maybe 1,000 of them in the past few years -- not one has had that hiccup. With that said though, except for high priority zero-days, we would actually roll ours up with our other patches so we can test them all together. There's only been a couple of times where we only did a smoke test and deploy def updates -- but we always do some testing on them. Always.
- barrkel 15y agoWhat if a business on the edge goes bankrupt because their internal web apps stop working?
- mitchty 15y agoTo be honest I see this as the canary in the coalmine for "enterprise" web apps. If they are so brittle as to be this dependent upon browser versions, versus throw the new version on a machine and run it through your browser tests with say selenium, how can it be depended upon? To me the root problem is internal web apps with atrocious testing, or more importantly lack thereof.
- zcid 15y agoIt's hard to blame the straw when the camel's back breaks.
- billybob 15y agoWhat if a business that wouldn't be feasible without companies adopting modern browsers becomes feasible when they do?
- omh 15y agoThe issue here is the mixing of new features and security updates. As a sysadmin, I would happily (and do!) roll out periodic security updates without significant testing, for the reasons that you outline. But when the software is deliberately adding/removing features, I have a number of reasons why I would be wary. You might remove a feature I was using, change the way that your features behave, or change the interface and cause confusion for users. I've seen cases of all of these, and if I wasn't actively managing the upgrade then we'd have had real-world problems that cost us time and (potentially) money.
- ZeroGravitas 15y agoIt's not that they don't know this, it's that they don't care. Corporations used to have so much power over tech adoption that this used to be the software developers problem and it cost them time and money. Now with growing consumerization (what version of Google Search did your IT dept. approve? Which iPhone browser version?) the balance of power has shifted and it's now the corporations' problem. Now that the pain point has been shifted it will soon become apparent to corporations that the current system is untenable, just as Chrome and Firefox discovered it was. The browsers couldn't change things except to pass the buck whereas the corporations can actually fix it, or be outcompeted by those that do (just as Firefox and IE were outcompeted by Chrome choosing this path). The third option for big corps. is to bluster and try and frighten Firefox into acting more like IE than Chrome by claiming it will hurt adoption if they don't do what they want. You only have to look at the Chrome, IE and Firefox usage graphs over the last few years to see which way Firefox should be jumping.