[citation][nom]deks[/nom]Not updating their software merely keeps them behind the times.I'm sorry, but corporations are supposed to adapt to new software and technology, not function in the dark ages.Sigh ... the IT departments in the firms are responsible of making sure everything works.Are they filled with incompetant people by any chance if an update from Adobe Reader leaves previous versions non functional?I would have to say so, because they run a much tightly controlled environment to begin with and these malfunctions shouldn't happen.Heck, they rarely (if ever) occur for home users.[/citation]
It's obvious you've never worked in a big company, as you really don't understand.
I do understand what you're saying, and for the uninitiated, it might even seem true. But, it's really a mistake, as I learned the hard way.
Change is bad, as a rule. It brings the possibility of unknowns that you don't have control over. There's an old saying, if it ain't broke, don't fix it. You have corporations that have established systems that are working for their employees, and when they don't work, there's a lot of experience dealing with that platform. Any software upgrades introduce bugs, and bugs there are less experience with. No amount of testing will reveal them all, or mitigate all the problems with change. So, you don't do it until it's really worth it, and in most cases, you get to skip releases and all the headaches associated with them.
For example, think of all the headaches that were missed skipping bad OS's like XP and Vista. I don't have Windows 7 yet, so I can't say for sure, but XP suck, and Vista sucked balls. A lot of companies stuck with Windows 2000 for a long time because it worked well. Some will have avoided the headaches and bad performance of XP and Vista, and move right to Windows 7. Some skipped IE 7, and if they wait, maybe even IE 8 with all its problems.
So, you really want to try to avoid change for as long as possible, unless it's got some compelling reason that makes it worth it. Microsoft, for reasons unknown to most, feel it's necessary to change the way things look with most of their releases, and this creates confusion for end users, and support costs.
You make change when you have to, not because someone likes to have the newest release of this and that because they think it's cool. That's what you do at home, not at work.
Having said all that, IE 6.0 is soooooo bad, unless internet access is a small part of the job (which it is in most places), I'd upgrade it. If you have apps that use the web, or need access, I'd say the pain involved in change is still worth it because using IE 6 is really bad. Although, IE 8.0 sucks bad too, but at least it's got additional useful features. Maybe companies are waiting for IE 9, who knows. It's really hard moving to something as bad as IE 8, even if it's better than 6.0.
Facebook
Twitter
Instagram