Slashdot Mirror


Who Is Still Using IE6? the UK Government

strawberryshakes writes "The death knell for IE6 was sounded a couple of years ago, but seems like some people just can't let go. Many UK government departments are still using IE6, which is so old — 11 years old to be exact — it can't cope with social media — which the government is trying to get its staff to use more to engage with citizens."

141 comments

  1. Behind the Times by Linsaran · · Score: 5, Funny

    Good to see the US government isn't the only ones.

    --
    In a bit of shameless internet panhandling, I accept Litecoin Donations at Lbd2oH9QsthD1GfuUXPyka12YxvWJYnBVf
    1. Re:Behind the Times by Ashenkase · · Score: 2

      Can add large sectors of the Canadian government to the list as well.

    2. Re:Behind the Times by SimonTheSoundMan · · Score: 2

      I've been to some large company HQs like Tesco and VW and even large offices for IBM, all still stuck to IE6.

      Brand new Tesco by me all their tills, stock control, e-mail, quite literally everything is done within IE6.

      Their software requires IE6 and they are not likely to change soon.

    3. Re:Behind the Times by AngryDeuce · · Score: 1

      A lot of retailers are stuck on IE6...I think it has to do with the industry's absolute hatred of ever actually spending money on internal improvements until it's become a ridiculous liability.

      I know from personal experience that CompUSA used IE6 before they crashed and burned, and Home Depot ran a lot of shit through it as well. At least at CompUSA the workstations weren't restricted from running other browser software, although we'd get bitched at about it from time to time when people would bypass the blocks and find ways to pull up pron on them...it was always a joy bringing a customer over to the workstation to show them the technical specs on a laptop to be greeted by a big old pair of titties when I opened FF.

    4. Re:Behind the Times by Anonymous Coward · · Score: 0

      Yup - still using it on our intranet.

    5. Re:Behind the Times by Master+Moose · · Score: 1

      And add NZ Governement Departments.

      One of our issues stopping a company wide upgrade is other software that has dependancies on IE6 that just aren't stable with 8.

      We have the same issue with upgrading office from beyond 2003 (so thankfully our IS department is yet to get the screams of "I hate this ribbon")

      --
      . . .gone when the morning comes
    6. Re:Behind the Times by hairyfeet · · Score: 2

      What I don't get is why MSFT doesn't just make it beyond simple to switch by offering an Intranet only IE 6 in a box. Something like a mini VM that ONLY works on the Intranet and ONLY to sites the IT guy has pre-programmed into the IE6 in a box. Because we all know its them damned IE 6 ActiveX Intranet sites that keep businesses on IE 6 and good luck getting them to spend the amount of cash it would take to replace it with an HTML 5 app.

      Now i apologize if MSFT has an offering like that but I haven't seen or heard of it, the only thing I have seen is VMs for web developers to try different versions of IE with. But those all work on the web which is not what you need here. What you need here is something that will drop an icon onto any XP/Vista/7 system when pushed through GP that will ONLY go to preset Intranet sites. That way the corps wouldn't have to replace their crappy intranet sites and when the user tried to surf off the intranet a little pop up would say "We're sorry but this is only for (insert Intranet site) would you like me to launch your default browser with (insert address) added?" and that would be that.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    7. Re:Behind the Times by LinuxIsGarbage · · Score: 1

      My company (a rather large multinational) requires IE for a number of internal apps. Even the Intranet site won't render properly on Firefox. Yet the outward customer facing website refuses to even try and load on IE6.

      Last year they actually officially released firefox (3.6) through internal software distribution channels, for general web browsing, and because new web apps (like new Oracle version) don't work on IE6. We also had problems when Firefox blocked Java. And of course days after sanctioning Firefox 3.6, firefox started running away with versions.

      I'm actually quite surprised. For a very conservative company in the past year we've gone Office XP (2002) - Office 2010, IE 6 - Firefox 3.6, Lotus notes 6.5-8.5, Windows XP- Windows 7 is in trials and will start rolling out Q4 (and will migrate away from Novell Netware).

      We'll still have PDP 11's, DecWriters, and VT220 terminals though.

    8. Re:Behind the Times by LinuxIsGarbage · · Score: 1

      It's quite surprising that unlike say MS Office, IE can't run different versions side-by-side. That causes people to use IE 6 for legacy apps, and Firefox for everything else.

    9. Re:Behind the Times by davester666 · · Score: 1

      Can't wait to apply for a passport and be told that one of the requirements for it is that you have to friend the teller...

      --
      Sleep your way to a whiter smile...date a dentist!
    10. Re:Behind the Times by Rasperin · · Score: 1

      You can sadly add a large list of private industry to it too, especially banks.

      --
      WTF Slashdot, why do I have to login 50 times to post?
    11. Re:Behind the Times by hairyfeet · · Score: 1

      Well you can with win 7 Pro, by using IE 6 in XP Mode and using IE 9 for everything else which is why i don't understand why they don't do something similar with JUST IE 6 instead of needing the full blown VM. It really shouldn't be difficult to put just IE 6 and just enough of the Windows underpinnings to support IE 6 in a VM based on an .exe that could be pushed with Group Policy.

      Hell I was making single app Windows back in the late 90s and early 00s for HTPCs by simply stripping out everything that wasn't needed for the media capture and then having a batch file load the app on launch. If i could do that back then without access to the code i don't see why MSFT couldn't do something similar WITH the code.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    12. Re:Behind the Times by cbiltcliffe · · Score: 1

      Home Depot may be using IE6, but the point of sale terminals at Rona (Canadian big box home improvement store, very similar to Home Depot) are still running Windows 2000.
      To upgrade from IE6, they'd have to upgrade their entire OS.

      --
      "City hall" in German is "Rathaus" Kinda explains a few things......
    13. Re:Behind the Times by cbiltcliffe · · Score: 1

      It's not surprising; it's intentional. Most of IE6 is implemented in various DLLs that are in \windows\system32\, with very little in the actual iexplore.exe file. That's the IE/Windows integration that the anti-trust trial was (partly) about.
      Side by side versions would result in conflicting DLLs being installed in system32, which would break things, similar to what happens if you replace some files on an XP SP2 machine with SP3 versions.

      --
      "City hall" in German is "Rathaus" Kinda explains a few things......
  2. but... by Anonymous Coward · · Score: 0

    They never buy NEW pc ?? Last time I installed some for my company I didnt had the choice, IE6 wasn't there...

    1. Re:but... by Joce640k · · Score: 4, Insightful

      New PC, old OS. Microsoft did a really good job locking people into IE. So good that many people still haven't escaped.

      --
      No sig today...
    2. Re:but... by Anonymous Coward · · Score: 0

      Still, last time I checked I couldn't buy license for XP...

    3. Re:but... by WrongSizeGlass · · Score: 1

      They never buy NEW pc ?? Last time I installed some for my company I didnt had the choice, IE6 wasn't there...

      FTFS:

      Many UK government departments are still using IE6

      Not all ... though even one is too many these days. Let's hope they don't have any IE 5 or old Netscape browsers hiding in unused bathrooms in the basement.

    4. Re:but... by RMingin · · Score: 3, Insightful

      Sure you can. Buy more than 100 seats of Windows 7 Pro, with Software Assurance, and self-downgrade before the initial install. Besides, most 100+ seat businesses use a custom OS image anyways. Easy enough to make it an XP Pro image, if you can find drivers for everything.

      --
      The preceding comment is my own, and in no way construes an opinon of the Emperor of Mankind.
    5. Re:but... by Joce640k · · Score: 2

      Governments have a way of getting special deals that aren't available to people on the street.

      --
      No sig today...
    6. Re:but... by Tridus · · Score: 2

      This is pretty standard in the Microsoft volume licensing agreement. There's lots of corporations doing the exact same thing. How do you think XP hung around so long after it wasn't for sale anymore?

      --
      -- "So they told me that using the download page to download something was not something they anticipated." - Bill Gates
    7. Re:but... by AngryDeuce · · Score: 1

      As can the humongous retailers that are buying tens of thousands of licenses at a time...

    8. Re:but... by denis-The-menace · · Score: 1

      And MS doesn't mind either because you buy 2 licences:
      -The OEM version that comes with the new PC
      -the Software Assurance version that bought extra.

      --
      Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
    9. Re:but... by RMingin · · Score: 1

      It's a damned good racket, but it can be done. Just give enough money to MS, and they'll let you do anything you want.

      Mind you, XP is solidly into security-patches-only support, and even that's drawing to a close, so I'd imagine the UK is looking into installing lots of firewalls over the next year or two, or they're even less intelligent than I gave them credit for.

      --
      The preceding comment is my own, and in no way construes an opinon of the Emperor of Mankind.
    10. Re:but... by jonadab · · Score: 1

      In practical, brass-tack terms, IE6 should be considered completely unsupported at this point and a grave security risk if you use it to access the actual internet.

      Using it for intranet-only stuff (presumably, because there's something proprietary in there that would cost a lot of money to upgrade or replace) does not present the same level of risk, provided you set it up so that IE6 can *only* access the intranet stuff, not the outside-world internet. (This can be done with judicious use of IE6's security zone policies.)

      But this is mostly a big so-what, because It's not like IE6 is useful for browsing the internet these days anyway: fewer than half of the websites on the internet will render successfully, and that percentage is falling rapidly now, mostly due to the lack of any significant amount of CSS support. Some sites also run into problems with IE6 because of the way it handled XMLHttpRequest, which is slightly different from how modern browsers do it. Sites that care about supporting IE6 can easily work around that, though. (IE6 *has* XMLHttpRequest; it's just accessed slightly differently. A simple wrapper function that tries both makes the problem go away.) The lack of CSS support is the larger problem, as it takes a lot of effort to work around, and most web content developers stopped bothering when IE6 usage share fell below 1% a couple of years back.

      Just for example, if IE6 is your only browser, you can forget about using any of Google's web-based services beyond the basic web search. YouTube, Gmail, Google Maps, Google Groups, you name it, they all don't work in browsers that old. Google is far from alone in this.

      Ironicially, it's so painfully hard to keep more than one version of IE installed at once, that organizations that still need IE6 will necessarily find themselves using a different browser altogether for accessing the actual internet, which is presumably not exactly what Microsoft had in mind when they worked so hard to get companies locked in to IE6.

      IE7 will not be far behind, I imagine. A couple more years, maybe. Currently my numbers say its usage share has already fallen below 5%, about _half_ of what it was one year previous. That's a very rough figure (based on usage of one site), but when you graph it over time the trend is absolutely impossible to miss: the IE6 share line is merging into the positive X axis, and the IE7 line looks like it's getting ready to follow. New version uptake for IE is faster than it used to be (probably due in large part to Automatic Updates being turned on by default since XP SP2). It still makes new version uptake for the webkit browsers look virtually instantaneous, mind you. But it's faster than it used to be.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    11. Re:but... by ChumpusRex2003 · · Score: 1

      They just put an old OS on. At the hospital I work at, there are a number of critical applications (like parts of electronic patient records, and other custom made apps) which only work on IE6.

      That means the brand new workstations we took delivery of last month (dual quad core Xeons, 4 GB RAM, Fire GL Pro cards) have all been loaded with XP 32-bit SP1, in order to get IE6 and avoid some features of SP2 which break a number of other apps.

      To be honest, it's a miracle that they're stable, as I can't believe the drivers for the graphics cards, etc. are fully supported on this OS.

    12. Re:but... by LinuxIsGarbage · · Score: 1

      You don't need Software assurance. New PCs sold with Windows 7 Pro licenses (eg the laptops and workstations businesses buy) come with Downgrade rights to WindowsXP pro.

      These businesses already have their XP Pro VL key and image, and are allowed to use it to reimage these new PCs to XP. You don't NEED a VL copy, you can use other versions, but activation becomes a PITA in a hurry.

    13. Re:but... by LinuxIsGarbage · · Score: 1

      I should mention you can do this reimaging without any additional charge. The Windows7 Pro OEM that came with the machine is the only incremental amount you give MS.

    14. Re:but... by Anonymous Coward · · Score: 0

      Nearly as ridiculous would be finding the Mozilla browser in use (not Firefox, but the browser that was just called "Mozilla").

    15. Re:but... by RMingin · · Score: 1

      That's true, I was mainly thinking of purchasing managers who will totally sign off on a huge package of SA Windows licenses because it makes audits simple, but then buy all the machines with Windows 7 Super-Cripple edition or the NoOS option. If you're careful to only buy Win7 Pro, you can downgrade from right there, no other purchases involved.

      --
      The preceding comment is my own, and in no way construes an opinon of the Emperor of Mankind.
  3. IE6 is so old! by WhatAreYouDoingHere · · Score: 0

    IE6 is so old.
    How old is it?
    IE6 is so old, when it was a kid, it never blew out candles on its birthday cake. They didn't have fire yet

    --
    "What are you doing here, Elijah?"
    1. Re:IE6 is so old! by Anonymous Coward · · Score: 2, Funny

      Dude, eleven isn't old.

      I'm forty-four and I can't cope with social media either.

    2. Re:IE6 is so old! by hendridm · · Score: 1

      Dude, eleven isn't old. I'm forty-four and I can't cope with social media either.

      If you were a web browser, you'd be featured in the Smithsonian, with maybe a small paragraph on Wikipedia on the history of web browsers, at best.

    3. Re:IE6 is so old! by Tarlus · · Score: 1

      Eleven is extremely old in Internet years.

      --
      /* No Comment */
    4. Re:IE6 is so old! by CastrTroy · · Score: 1

      I'm not sure I'd qualify IE 6 as 11 years old . Sure it was released in 2001, but until October 2006, it was the only browser offering from Microsoft. So I think that I would almost like to say that it's less than 6 years old. That is, if you were in charge of IT at some company, and you had to standardize on a browser in January 2006, what would you have chosen? Chrome wasn't out.Firefox (1.0) had just been released a bit over a year before that. So a bunch of goverment departments haven't changed browsers in the last 5 years. So what. It's not that surprising.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    5. Re:IE6 is so old! by Billly+Gates · · Score: 1

      Shoot IE 8 just supported 1998 CSS 2.1 standards. The frustrating thing is all the other browsers are cutting edge now. IE 9 is ok, but that long lapse shouldn't be an excuse. Ms should be ostracized for it!

      Imagine a world where we had to still support gcc 2.95 and VC++ 5, but it also had to compile in GCC 4.6 and VS 2010, and made sure all our code would compile flawlessly without error between those 2 versions? The changes in C++/C are huge with STL support and so on.

      The whole point of switching to intranet apps was to avoid a nightmarish scenario like this. They were promised that it was write once, no need to deploy, anywhere forever. It turns out it is easy to upgrade legacy desktop apps then it is for intranet sites.

    6. Re:IE6 is so old! by hobarrera · · Score: 1

      Firefox's distant relative, Netscape existed at the time, I remember using it back in 1999, so IE wasn't the only choice.

    7. Re:IE6 is so old! by Billly+Gates · · Score: 1

      Yikes, Netscape's CSS support made IE 6 look like a compliant saint.

      Webmasters back then made sites that looked liked Craigslist and stuck with tables and HTML because Netscape blew so bad. I eventually switched to IE 6 in 2002 and couldn't believe the difference and how much better it was and faster. It sucked goatballs of course but back then what choice did you have? Netscape 4.7 came out in 1998 was already 4 years old! Just a minor improvement over Netscape 4.5 which came out in 1997.

      By 2001 Netscape was becoming obsolete fast and was worse than IE 6 if you can believe anything was worse. It wasn't until Firefox that anything was even better.

    8. Re:IE6 is so old! by CastrTroy · · Score: 1

      Yeah, but looking at the usage history it wasn't very widely used in 2006. So, while it still existed, no competent IT person would have recommended it for company wide deployment. If you look at Usage data for Q1 2006, you'll see that IE is up around 90%. This is why IE 6 is still around. Because for a 5 year period after it's release, IE was used by more 85% of users.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    9. Re:IE6 is so old! by whoever57 · · Score: 1

      That is, if you were in charge of IT at some company, and you had to standardize on a browser in January 2006, what would you have chosen? Chrome wasn't out.Firefox (1.0) had just been released a bit over a year before that. So a bunch of goverment departments haven't changed browsers in the last 5 years. So what. It's not that surprising.

      There is a huge difference between specifying the default browser for the desktop and specifying a web app should only work with that browser. One is a reasonable decision, the other shows a lack of vision.

      --
      The real "Libtards" are the Libertarians!
    10. Re:IE6 is so old! by camperdave · · Score: 1

      I'm not sure I'd qualify IE 6 as 11 years old . Sure it was released in 2001, but until October 2006, it was the only browser offering from Microsoft. So I think that I would almost like to say that it's less than 6 years old.

      So, your 11-year-old child would only be five because she didn't have any siblings until six years ago? Good luck with that.

      --
      When our name is on the back of your car, we're behind you all the way!
    11. Re:IE6 is so old! by drinkypoo · · Score: 2

      So, your 11-year-old child would only be five because she didn't have any siblings until six years ago? Good luck with that.

      No, see, that's how it works with computer software; the date we're interested in isn't the date of introduction but the date of supersession. In this case that was only six years ago. Until, say, a year before that tops it didn't make sense to try to aim for IE7, and if you were committed to using a platform browser you were therefore targeting IE6. I was glad someone had figured out what year all this had happened because I didn't want to look it up.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    12. Re:IE6 is so old! by plate_o_shrimp · · Score: 1

      So, your 11-year-old child would only be five because she didn't have any siblings until six years ago? Good luck with that.

      No, see, that's how it works with computer software; the date we're interested in isn't the date of introduction but the date of supersession..

      IE 5 for Mac had no successor -- does that make it brand new still?

      --
      This sig has exceed its monthly bandwidth allotment.
    13. Re:IE6 is so old! by camperdave · · Score: 1

      So, I guess it all boils down to the definition of superceded, because there were plenty of browsers around when IE6 was introduced: Netscape, Galeon, Opera, Konqueror to name a few. I guess for some it will never be superceded, because of the craptastic ineptitude of the website designers they hired to write their intranet portals.

      --
      When our name is on the back of your car, we're behind you all the way!
    14. Re:IE6 is so old! by CastrTroy · · Score: 1

      The point is, that in 2006, IE had 90% market share. And even in 2008 it had close to 80% (Based on this data). So designing a web application that only worked in IE at the time could have been seen as a not-so-bad business decision, all things considered. Sure you could design something that worked in "all browsers" which at the time was just about nobody else. Why spend all that time testing on a browser that virtually nobody used. Also, remember the feature set wasn't as rich as it is now. If you wanted to do something like an AJAX call, you could do it using an ActiveX control, a Java applet, or possibly flash (I can't recall). But there was no native way to do that in the browser. A lot of internal applications were built with ActiveX, because it gave a very rich feature set, at a time when Javascript was a complete mess.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    15. Re:IE6 is so old! by hairyfeet · · Score: 1

      That is why I had my users on the Moz Suite back then followed by Seamonkey which a few use still. Even back in 06 one could see that most of the patches coming out were for IE 6 and the browser had a giant target painted on it.

      That is one of the truly wonderful things about today in that there is plenty of choices out there. Today I give my customers a choice of Comodo Dragon (Chromium based without the phone home), Pale Moon (an offshoot of Firefox that isn't gonna use the metro UI, great for those that prefer the Fox), for older machines Kmeleon CCF Me or QTWeb, both of which are VERY fast even on older hardware. If anyone is tired of their browser they should give one of the above a try, they all have their advantages.

      I'm just glad i'm not doing corporate anymore because it must truly suck ass to have to support IE 6 in this day and age.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    16. Re:IE6 is so old! by drinkypoo · · Score: 1

      So, I guess it all boils down to the definition of superceded, because there were plenty of browsers around when IE6 was introduced: Netscape, Galeon, Opera, Konqueror

      Many organizations were cowed into depending on a Microsoft-only platform, so none of the alternatives really applied for them, and since that accounts for shitloads of seats and users today, they are highly relevant. If you were drinking the Microsoft Kool-Aid you were anti-Netscape, and none of those alternatives were really credible alternatives at the time. These days, Webkit and Opera are both highly credible, I'm not trying to badmouth anything, but back then realistically it was between Nutscrape and Aieeee! And frankly, there were plenty of reasons to complain about both browsers — which in both cases have, I feel, been pretty much completely replaced with new things to complain about :)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    17. Re:IE6 is so old! by Anonymous Coward · · Score: 0

      Ok, but what of that has anything to do with the definition of how old something is?

    18. Re:IE6 is so old! by drinkypoo · · Score: 1

      Ok, but what of that has anything to do with the definition of how old something is?

      The last time something was shipped when its successor was not available a download away is its age. Check out how old Windows XP is by this definition (shipped on many small systems until very recently) and be agog.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  4. Schools by Anonymous Coward · · Score: 0

    my school in Germany also uses ie6. but well it is just a school, but because it is an integrated part in the it system of the town it is likely, that ie6 is used there as well.

  5. Link to Goverment document by wilfie · · Score: 3, Informative

    The "Social media guidance" document on which this is based is an interesting read: http://www.cabinetoffice.gov.uk/resource-library/social-media-guidance

  6. Let go? by Anonymous Coward · · Score: 5, Insightful

    It's not about "letting go" - I'm sure it's about the cost of upgrading thousands (tens of thousands?) of systems. Not just the licensing of the software, but also the cost of execution and management of the upgrade, and then the upgrade of all the applications, training on new versions, rewriting an ass ton of security and management policies, and years of churn getting the kinks out of thousands of systems, and the loss of productivity while switching over, and... (I'm sure with a couple more minutes thought I could come up with five other angles of cost).

    The summary makes it seem like they're holding on for sentiment, and that they're shooting themselves in the foot by sticking with tried and true software. The summary hasn't given any voice to the enormity of the task (it's not a simple "derr, click the upgrade button stupid"), nor the idea that this is government money which can and arguably should be used in more critical areas of life.

    Are slashdot editors really this shortsighted?

    1. Re:Let go? by jones_supa · · Score: 1

      One could still think that the time would have come to suck it up and pay the cost for a bigger upgrade, just to not be using ancient systems forever.

    2. Re:Let go? by Wulfrunner · · Score: 5, Insightful

      I recognize you! You work for the [insert government here] ITS department down the hall from my office. You and your just adequate, barely competent colleagues are the reason I'm stuck with a brand new, yet somehow still limping, T520 that takes four minutes to start. You are the reason I can't "exceed the level of my cluster". You are the barrier to innovation. The attitude you just espoused is the reason our monolithic organization is stuck in the stone age. How is it that you guys can take five years and one billion dollars to develop an application that is buggy, user un-friendly, doesn't do the job it's supposed to, and cripples the department it's supposed to be helping by eating their entire IT budget. You and your colleagues have never heard of Brooks' law, are complacent, risk averse, and unimaginative. I hate you.

    3. Re:Let go? by Anonymous Coward · · Score: 4, Interesting

      Don't go blaming the IT departments so quickly. Blame the contractors, and those who purchase said contracts. While I can certainly point fingers at some terrible in-house public sector IT departments, they're not all bad, not by a long shot.

      I'm posting AC for business confidentiality reasons: my company provides web software (business stuff, not the main site) for the UK National Institute of Health Research. They're our first (and only) public sector client. I had to liaise quite a lot with the previous supplier, with regards to migrating data out of the old system. I simply could not believe how awful it was. It seemed to be designed from the ground up to require maximum maintenance, and apparently there were 5 staff members at the contractor who worked full time on supporting the business logic. Not on updates or new features, just on keeping it working.

      When we were negotiating the contact with them, they wanted a clause that said if we failed to provide them with any software at all, they got 50% of their money back. That shocked us. Just how bad is the public sector IT culture that they felt they'd only be entitled to half their money back if they got nothing for it?

      The previous suppliers told us they wouldn't be able to provide the data extracts we required until several months after the go-live date, so we then entered into a big wrangle to let us get a copy of their database and do it ourselves. This was a wrangle because they wanted to protect the "trade secrets" or "intellectual property" of the data model itself. Which was awful btw; I ended up with a 35-page print out of it sellotaped together on the wall, manually drawing in lines where all the foreign keys ought to have been.

      We got the migration done to the client's satisfaction in the end, but this wouldn't have been possible without a bunch of IT guys at NIHR's end who were pretty damn competant, and very willing to get stuck in. I can't say as much for the contractor's guys, though. We ended up with a TUPE case against us, with them arguing that we had a legal obligation to hire them on, even though we were providing a completely different system (i.e. one that worked).

      Anyway, that's a bit of a rant. In conclusion, if IT seem like they're a wee bit shit, then they might be, or alternatively, they might be having to deal with a lot of shit from elsewhere.

    4. Re:Let go? by Wulfrunner · · Score: 2

      Yes you've got a valid point -- procurement in government is just as broken as the overall IT infrastructure. On the other hand, if someone isn't willing to raise a stink and put their job on the line to prevent a disaster of that nature, they don't deserve to call themselves a public servant. The "lowest bidder" is not the same thing as the "best value", and you have to be willing to fight for what's right.

    5. Re:Let go? by Billly+Gates · · Score: 2

      IE 6 was a great bet to make in 2003.

      If you read Hall of Fame stories on slashdot there is one called what keeps you on Windows? IE 6 and how great a browser it is was a top response. Compared to Netscape IE 6 was years ahead with this new thing called CSS.

      There was no Firefox, Safari, or Chrome back then. People were betting on standards and it was easily assumed that the MS box model and VBscript would be used today just like people view Windows. Shamefully, after reading about how great IE 6 was on slashdot I started using it too in 2002 - 2004 before Firefox .7(phoenix).

      People tend to remember the past differently based on the present and its thinking XP is the best OS ever today after encountering Vista, to the oppose with IE 6 which is a piece of crap in 2012.

      Don't blame the contractors as betting IE 6 was the logically thing to do until about 2007 are so when Firefox appeared it could actually compete and not be a fringe geek thing. Many websites too only worked on IE 6 or complain that you were running Netscape and used tables and no CSS at all if you used early Firefox or Mozilla until about 2008.

    6. Re:Let go? by Anonymous Coward · · Score: 0

      just read an article about a large bank that still does most paper work on WP5.1, they had no intentions of changing that, it still works and it would be an enormous
      task to reimplement it on something else.

       

    7. Re:Let go? by Xest · · Score: 1

      The British army is one of the culprits, I know this because we've developed software for them and still have to support IE6 to this day. They have plans to do away with it but they just get put back further and further.

      The problem is how, in a time of budget cuts, can you possibly justify upgrading every computer in the army to IE6 vs. making sure your soldiers fighting in Afghanistan have body armour, helicopters to avoid IEDs and so forth?

      It's just not a priority. The threat of cyber attack causing any actual measurable harm is negligible compared to IEDs etc. - even something on the scale of Wikileaks'/Manning's US cable leaks did less harm to people's lives than the odd IED here or there has done.

      Upgrading IE6 is something the army can save for peace time when they get the fuck out of Afghanistan and are sat around with nothing better to do and nothing better to spend their money on.

    8. Re:Let go? by Anonymous Coward · · Score: 0

      You make a lot of sense. I used IE6 until 2004. It was actually quite fast when it came out. I heard about Mozilla Firebird, so I downloaded it and it turned out to be shit. It was slow, kept crashing, did something weird with HTTP that got me banned from an online game I used to play, etc. I then got introduced to Opera, which I still use to this day, but since Opera 7 didn't work with 20% of sites, I had to use IE6 for much longer. I only really started using FF as my "compatible" browser in 2008.

    9. Re:Let go? by BumpyCarrot · · Score: 1

      Are slashdot editors really this shortsighted?

      "Posted by timothy"

      'nuff said.

      --
      Do you see what I did there?
    10. Re:Let go? by ChumpusRex2003 · · Score: 1

      One of the difficulties is that priorities in government sector procurement are often biased in favour of the senior management and doing what is seen to be good politically, rather than usability or manageability.

      The difficulty with the govt tender process is that some vendors are unfamiliar with it and don't give the best answers to the questions asked in the initial tender documents.

      E.g. I've just been involved with the procurement of a PACS system (digital X-ray archive), and a lot of the vendors simply scored 0 on a large number of points when they returned their responses to the original specification document.

      For example (these are not verbatim examples, but fictional examples which I believe accurately depict the problem):
      Tender question: Describe how the software ensures compliance with the Data Protection Act (DPA).

      Typical bad answer: The software is compliant with the DPA.
      (This is a totally meaningless answer - as a result the vendor scores 0 on this specification point).

      Typical good answer: The software has features that assist the hospital in meeting the following aspects of legislation: Control of access, control of retention, Prevention of disclosure and assisting staff in preparation of subject access requests.
      Control of access: The software provides for password, certificate, hardware token or active directory authentication. There is a role based permissions system with arbitrary complexity - for example, a nurse's login could be restricted to access of patients only on her ward. Permissions can be controlled on a role or user level, and can provide access control on any image, case-record metadata (including custom fields) or metadata available from a connected information system.

      Control of retention: Data can be destroyed automatically when no-longer needed. The period can be configured by the local adminstrator according to local policy. A rules-engine is included which permits granualar control of retention based on, for example, patient age (children's examinations can be kept until adulthood, instead of on a data age), type of exmaination (e.g. research studies may need longer retention), manual flags, any image metadata, or metadata from a connected information system.

      Prevention of disclosure: All data stores are encrypted with 256-bit AES. Data transmission over the LAN, or public networks, are encrypted using TLS 1.1 with 256-bit AES. If data caching on client machines is permitted by the administrator and local policy, the data is encrypted using 256-bit AES. All system accesses are logged in an audit-trail. Powerful analysis tools, including a rules-engine, are provided to allow investigation of suspected abuse. If the system administrator permits images to be saved to teaching files/powerpoint documents/etc., image metadata containing patient identifiers will be removed automatically. If the images contain patient identifiers in the pixel data, then the images will be redacted automatically (subject to the availability of appropriate metadata in the original image files).

      Subject access: The system can provide a full subject access report for both patients and users (staff). The report will include all data, including audit trails, together with summary (the staff report will have patient data redacted automatically), and can be exported to optical disc or hard drive in a single operation.

      With an answer like that, it has to score 10/10.

      The problem is that most of the software vendors are not very good at understanding the questions - particularly, where they relate to legislation. The big winners here tend to be the big contractors, often infamous in the national press for supply of poor quality solutions. They "get" what the questions are asking, so score big - and this often makes up for less-than-stellar performance in the technical and usability sections of the scoring.

    11. Re:Let go? by Anonymous Coward · · Score: 0

      The summary hasn't given any voice to the enormity of the task (it's not a simple "derr, click the upgrade button stupid"), nor the idea that this is government money which can and arguably should be used in more critical areas of life.

      Are slashdot editors really this shortsighted?

      Government money can be, has been, and will continue to be spent on plenty of things more frivolous, stupid, or shamelessly pork barrel than a much needed software infrastructure upgrade.

    12. Re:Let go? by AmiMoJo · · Score: 1

      IE9 is a critical security upgrade for IE6 users. Even with anti-virus software bring the machine to its knees a user running IE6 is basically screwed. It is almost always less hassle to upgrade to IE9 then it is to deal with all the IE6 related infections.

      I have seen IT departments refuse to skip security patches for fear of the updates breaking stuff, and they get away with by blaming the users for getting infected.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    13. Re:Let go? by Anonymous Coward · · Score: 0

      You can't upgrade IE6 to IE9. IE9 isn't supported (and won't install) on WinXP; WinVista and Win7 came with later versions of IE. The only upgrade path from IE6 to IE9 involves an OS upgrade in the middle.

      - T

  7. Yeah, tell me about it by jholyhead · · Score: 5, Interesting

    I'm a web developer for an organisation that builds web based software that is primarily used by UK local government departments.

    IE6 is my nemesis.

    A lot of these local authorities are slowly starting to upgrade to Win7 platforms (just in time for Win8), but just like a chain being only as strong as it's weakest link, we have to ensure we are developing for the slowest common denominator.

    From the dozens of conversations I've had with Council IT teams around the country, it isn't a lack of will or of motivation or of education, but of a real (and partially justified) fear that if they upgrade to Win7, some essential legacy web based application that works flawlessly in IE6 and XP, will fall over when introduced to IE8. This has happened at various places around the country and has cost Councils a pile of money to fix the issue or to replace those legacy systems. In the post recession cost-cutting world, no one wants to be the guy who lands their employer with a huge bill. I expect we wont see the stragglers taking up the challenge until austerity is done and dusted.

    And there you have it. I managed to make this all the coalition government's fault. My work here is done.

    1. Re:Yeah, tell me about it by Anonymous Coward · · Score: 0

      XP Mode. If they fail, it's indeed the government IT's fault - for not deploying it with the XP machine included.

    2. Re:Yeah, tell me about it by Anonymous Coward · · Score: 0

      Yeah the problems are that the government

      1) feels the need to upgrade what isn't broken - there is no need for employees to "interact with social media" or such bullshit;

      2) has fired all its civil servants so businesses with friends in the civil service are given work instead.

    3. Re:Yeah, tell me about it by Sparticus789 · · Score: 1

      It's a simple choice really. They can upgrade and modernize the systems or they can go back to pen and paper. Just take away Parliament's salary for a month and that would pay for the upgrades.

      --
      sudo make me a sandwich
    4. Re:Yeah, tell me about it by Anonymous Coward · · Score: 0

      Running systems in parallel until everything works as expected seems like the normal solution, nut every goverment system seems to move wholesale to the new system and then pretend the old one has died in a road accident and can never be used again.

    5. Re:Yeah, tell me about it by Just+Some+Guy · · Score: 2

      From the dozens of conversations I've had with Council IT teams around the country, it isn't a lack of will or of motivation or of education, but of a real (and partially justified) fear that if they upgrade to Win7, some essential legacy web based application that works flawlessly in IE6 and XP, will fall over when introduced to IE8. This has happened at various places around the country and has cost Councils a pile of money to fix the issue or to replace those legacy systems.

      GOOD! Those same groups didn't want to listen when we told them that writing to a single browser with it's non-standard quirks and single-platform pathogen vector of a plugin architecture was a bad idea. I'm going to use this as a warning to my clients: "you don't want to write this to run on IE-only. Remember what happened with IE6 and how much it cost to fix that boondoggle?"

      --
      Dewey, what part of this looks like authorities should be involved?
    6. Re:Yeah, tell me about it by Just+Some+Guy · · Score: 1

      1) feels the need to upgrade what isn't broken

      IE6 is very, very broken. Fortunately for us (and unfortunately for people who have to use it), it's also almost completely dead. The day is coming when it will be literally impossible to run an IE6-compatible system without buying expensive legacy-compatible hardware or hosting it inside an emulator.

      Consider that IE6 on Windows XP was released in 2001. Two years from now, this will be as ancient as using IE5 (released in 1999) on Windows 98 would be today. Can you imagine how fun it'd be to have to support that combination in your IT department? Can you even buy new hardware that would boot Windows 98 outside of specialty orders? Would you really want to host VMWare, etc. on the desktop of every user who needed it? Well, we're within not-so-many months of that being the same situation for IE6 on XP. Yeah, I can see why someone might want to "upgrade what isn't broken", even if you miss the Good Old Days.

      --
      Dewey, what part of this looks like authorities should be involved?
    7. Re:Yeah, tell me about it by acoustix · · Score: 1

      XP Mode. If they fail, it's indeed the government IT's fault - for not deploying it with the XP machine included.

      Yeah - let's kick the can further down the road. That will solve the problem!

      --
      "A plan fiendishly clever in its intricacies"- Homer Simpson
    8. Re:Yeah, tell me about it by WankersRevenge · · Score: 1

      A lot of these local authorities are slowly starting to upgrade to Win7 platforms (just in time for Win8), but just like a chain being only as strong as it's weakest link, we have to ensure we are developing for the slowest common denominator.

      I see this point of view a lot with web developers and when fully realized, it means that you're stuck writing markup and scripts that are a decade behind current standards.

      I argue the reverse. Write for current browsers but provide support for older browsers. That way, you remain current as a developer. Besides, with IE conditionals and writing scripts that check for features as opposed to implementation, IE6 really is not that big of a deal. I find the the hard part is supporting older versions of FireFox or Opera or developing pages that gracefully fail without ruining my user's experience. .

    9. Re:Yeah, tell me about it by Billly+Gates · · Score: 1

      The problem is it is not broken at all to the accountants.

      CNN, MSNBC, and all the corporate websites that people use at work all work fine with it. Why upgrade to something we already have? Until these sites stop working the PHBs and the finance people will demand users stay on IE 6 so the share price can keep going up some more.

      Trust me to these people we *would* still be running Windows 98 until the end of time and *never* upgrade ever. That costs money after all and we are in the x business. Not an I.T. company so its all a cost center anyway that ads no value etc.

      Google is making steps. I fired up my IE 6 in a VM and noticed a couldn't even check my gmail anymore. I hate the new style but I give a bravo to Google for forcing these users and giving them a reason to upgrade crying and screaming like a todler. Unfortunately, these coompanies will just use Office265 and cancel Google Docs so they can keep IE 6 and XP just a little longer sign.

    10. Re:Yeah, tell me about it by Bob+the+Super+Hamste · · Score: 1

      Isn't that how all governments operate, especially when it comes to debt and spending.

      --
      Time to offend someone
    11. Re:Yeah, tell me about it by Billly+Gates · · Score: 1

      Are you crazy?

      IE 6 is not just a decade old. Its DOM is different, its box model is different, the way it wraps text when a box is full is different, its javascript is different, and I could go on and on.

      I am learning IE 6 now and let me tell you I can't make a site look as good. Sure I can get a butt ugly basic site with no floating css or shadows or any graphical animations in CSS 3 and use hacks like CSSPIE which slow IE 6 down to glacial speeds. This does not count the bugs.

      I see the bean counters view it just works but until you stop supporting IE 6 they will see your site and say AH HA its fine! That billy gates was wrong saying IE 6 is a PITA. Other web browsers sucked too and were not standards compliant in those years including Opera and old Firefox.

      Don't support them. Opera is not that great and not used outside of Russia and not worth the hassle to support in the US. I am only learning IE 6 because my business idea supports enterprise users. I will support FF 3.6 as many still use that but nothing older. Next year these corporations will finally be upgrading to IE 10 and getting ready for the EOL. I will finally cancel all support for FF 3.6 and IE 6 & 7 as these are legacy images.

    12. Re:Yeah, tell me about it by Anne+Thwacks · · Score: 1
      Running systems in parallel until everything works as expected seems like the normal solution,

      Piloting things before nation wide deployment is also fairly normal but this is government we are discussing. Normal is not part of the scenery.

      --
      Sent from my ASR33 using ASCII
    13. Re:Yeah, tell me about it by Just+Some+Guy · · Score: 2

      The problem is it is not broken at all to the accountants.

      Then I think those accountants are inappropriately insulated from the pain of their decisions. If decade-old software is good enough for other employees, then Office 2000 should be good enough for them.

      --
      Dewey, what part of this looks like authorities should be involved?
    14. Re:Yeah, tell me about it by Billly+Gates · · Score: 2

      I am beginning to resent them greatly. Accountants are also making critical medical decisions and ordering doctors on what to do if you have a crappy HMO as well. Accountants are the ones making almost every business decision and who are becoming the next CEOs.

      They are great at reducing costs and that is it. Of course the accountants have Office 2010 they are a profit center and unlike you and I are very important people. But IT, UGH go back to putting out fires, we have real work to take care of etc.

      Meanwhile they are dumbfounded when the network goes down and when customers go to competitors due to the low quality brought by excessive cost cutting. Accountants should make accounting decisions and it is ruining business for the last 10 years.

    15. Re:Yeah, tell me about it by qu33ksilver · · Score: 1

      Same here bro! High five to that. Working CSS in IE6 is a real nightmare. I have to split my hairs to find out the most cumbersome CSS hacks for the site to work in IE6. Support for IE6 should be really stopped. The amount of effort we developers spend to make it work in IE6 is much more than if the users were forced to move out of IE6. True story.

    16. Re:Yeah, tell me about it by Anonymous Coward · · Score: 0

      Sometimes facebooking the UK immigration people pushes your visa application a bit further. My neighbour has tweeted his electricity company (OK not government) and got a problem fixed that 2 hours on the phone didn't.

    17. Re:Yeah, tell me about it by WankersRevenge · · Score: 1

      Inconsistency is one thing all browsers share and if you are a developer worth your salt, you learn to innovate around them instead of blaming the technology. And yes, if the bean counters use ie6, you support ie6.

      Like I said, by using conditionals to produce extra markup and load css sheets, support isn't that difficult. I also recommend you learn the try/catch block in javascript which is present in IE6.
      .

    18. Re:Yeah, tell me about it by Anonymous Coward · · Score: 0

      E6 is very, very broken.

      It works in precisely the same way it did when it was "new". It Runs web based applications using ActiveX. The webapps have been upgraded a long way but they were and still are written specifically to support IE6 only. We have been told to try out IE7 with some of them now and that is pretty dire. They will not even look at modern browsers - we have tried but blank white boxes are not terribly useful.

      "Why didn't anyone point out that using IE6 and Activex was not the best idea?" you might ask. Many of us did. So did those in senior positions at the time. This was laughed off by highly paid experts who knew that MS, IE6 and ActiveX was the future and anyone who thought different was incompetent and or "tecchies". There is a complete dismissal of competence and knowledge amongst those at the top. I understand that this is not just the UK but most civil services have the same problem. The people in charge consider background knowledge a beacon of unsuitability for a post. Go and watch Yes Minister. It's still true.

    19. Re:Yeah, tell me about it by Anonymous Coward · · Score: 0

      Oh shut up. Old Operas and FFs were generally quite standards compliant. If something works in FF it will work in the latest Opera, unless you use the -moz extensions, so you don't need to bother "supporting" Opera. Also, Opera modifies itself to deal with crappy sites (like the ones designed by you).

    20. Re:Yeah, tell me about it by jholyhead · · Score: 1

      Most choose to run an initial pilot with a few hundred users, then, after 6 months or so of successful running, they'll begin to transition over. It can still take 2-3 years from the decision being taken to the final user being upgraded.

      So the upshot is, people like me will still have to work with IE6 for at least a couple more years.

    21. Re:Yeah, tell me about it by jholyhead · · Score: 1

      About 1/2 of our users use IE6 either because their IT team don't allow them to use anything else or because the users don't know anything else exists. 50% of your user base is that much of a big deal.

    22. Re:Yeah, tell me about it by Anonymous Coward · · Score: 1

      While you are making separate CSS and doing regression testing, I am making twice the amount of websites doing things that would require flash on your browser, using text shadows, smooth rounded corners, and AJAX that your browser can't handle which works on any modern browser. It will blow yours away.

      Please stop supporting old browsers. You are working for free and endangering the security of your workplace and internet and putting external costs onto yourself by giving up your free time after 5pm and the free time of other web developers so the cost accountants can get their bonus.

      It is time to let things go and IE 6 was one of the worst products ever made. Image what world we would be in if we had to support Netscape and IE 2.0 today? In the old days people upgraded their browser every year and it is returning to that today.

      Enough

    23. Re:Yeah, tell me about it by Billly+Gates · · Score: 1

      Whats the website?

      The statistics I see tell Ie 6 having 1% of all users in the US.

    24. Re:Yeah, tell me about it by Anonymous Coward · · Score: 0

      So if developers program with emphasis on backwards compatibility, do they spend less thinking of the future? It's a genuine question, as my first thought is that it's the local authority IT dept's fault for not planning ahead.

      If it's a vicious circle, then what is the answer?

    25. Re:Yeah, tell me about it by jholyhead · · Score: 1

      It's an intranet web application.

    26. Re:Yeah, tell me about it by StormReaver · · Score: 1

      I laugh every time I hear someone say something like, "we can't upgrade because, despite all the warnings over the years about bad development practices, we coded our web infrastructure on non-standard misfeatures/bugs of a single browser and version, and now those misfeatures/bugs are fixed in subsequent versions in this browser. If we had designed around actual standards, we would have been fine, but that was just a little bit harder than sacrificing the future."

      It's nice to see stupidity justly rewarded.

    27. Re:Yeah, tell me about it by AmiMoJo · · Score: 1

      We have a load of older apps we use for software development and electronics that only works on XP, meaning we have to keep XP machines around just for that. Old hardware that doesn't work on Windows 7, buggy software that even XP Mode can't fix... It's a pain but the only option is to replace all that stuff at great expense.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    28. Re:Yeah, tell me about it by WankersRevenge · · Score: 1

      Please, mr coward - I'm the guy who reads the specs. I'm the guy who pays close attention to stuff as they are developed so my users to get experience new standards as they are implemented. I'm also the guy who builds his sites to gracefully degrade so people with older browsers can still read the content because at the end of the day, that's WHAT USERS WANT TO DO.

      Sure, my sites take longer to create but they work in real world conditions whereas yours probably flops like a dead fish the moment a user exceeds your narrow specifications. Do yourself a favor, turn off JavaScript, and check out your sites. Now do your users a favor and make it work. Living up to higher standards takes work but your audience will appreciate you for it. Mine certainly does.

  8. Same Story in Germany by nicovl · · Score: 1

    In Germany most IE6 users also come from government institutions... I guess that with the general laziness of IT admins, we shouldn't be surprised that the ones working for the government are the laziest :)

    1. Re:Same Story in Germany by Shadow99_1 · · Score: 4, Interesting

      As a IT admin, I can attest we are not all lazy. It more often then not is a matter of pulling upper levels of the business kicking and screaming into modern times by spending some money to make sure things still work. They would often rather spend tons of money maintaining old OSes on modern hardware then make sure old software they feel is critical actually gets fixed to work on modern OSes.

      It's even crazier when they then want some ancient IE6 based web app to miraculously work on their shiny new Ipads and don't understand that they simply won't work. I have had a a CEO complain that we need to put IE6 on his Ipad because he needs to run X web app that was made 15 years ago and only works in IE6. He refused to accept that an Ipad will not run IE6, to the point where he even cursed at us and demanded we install Win XP on his Ipad to 'make it work'.

      Most of us IT admins know that we have to get this stuff working and get them off of systems often setup before we were even hired. Getting large businesses and governments to do such things though is at times futile.

      --
      we are all invisible unless we choose otherwise
    2. Re:Same Story in Germany by Anonymous Coward · · Score: 0

      If the problem is specific old web applications, wouldn't an easier path be to install e.g. firefox as the default with e.g. IETab configured to show those specific urls using IE?

    3. Re:Same Story in Germany by Anonymous Coward · · Score: 0

      um, I would hope you don't work in IT actually. Remote desktop to an xp client. Done and done.

    4. Re:Same Story in Germany by Nimey · · Score: 1

      You can do that, but the experience is sub-optimal. We've got a few users doing just that with iPads to access a certain program that was written against a (modern) version of IE.

      It's slow and the UI is /not/ meant for touchscreens, but it does work.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    5. Re:Same Story in Germany by Billly+Gates · · Score: 1

      If I were Balmer I would port IE 6 for the enteprise version of Windows 8 to give it a competitive advantage in corporate America as well as include the usual modern IE 10.

      Without the tie in with ancient compatibility why buy a Windows 8 mobile device or phone? IPhones already have this functionality and once these ancient web apps are upgraded they will work on your top man's IPAD. Then what? No more Microsoft needed.

      Worse they are porting Office to the IPAD which is another mistake.

    6. Re:Same Story in Germany by Anonymous Coward · · Score: 0

      on iPad? IETab merely uses current IE rendering engine which is not available on iPad. It is not a renderer in itself. If you didn't know this, turn in your geek card and get off my lawn.

    7. Re:Same Story in Germany by jfdavis668 · · Score: 1

      It's the same where I work. It isn't the IT people who are holding up upgrades, it is the workforce. People scream if you make the slightest change to what they use. We still use XP, and had to fight tooth and nail to get them upgraded to IE 7 and Office 2007. I don't know what will happen if we ever try to deploy Windows 8. It's not all of them, but enough to hold up the process.

    8. Re:Same Story in Germany by Bob+the+Super+Hamste · · Score: 1

      It isn't just technology that managers seem to be incompetent with. My dad works in a hospital as one of the techs who fix and maintain the machines and the managers he has had are just as worthless. He has had ones who never bother to keep up to date on status reports and complain about how far behind they are on PMs but the report the manager was looking at was 2 weeks old. One complained that they needed to cut costs since their department wasn't showing a profit and asked the question "Do we really need to keep ordering this much anesthesia machine hose?" Another one didn't want to have his department spend the $700 to repair a $16,000 machine as the department that the machine belonged to could have replaced it and spent their money instead.

      --
      Time to offend someone
    9. Re:Same Story in Germany by Anonymous Coward · · Score: 0

      That's fine.

    10. Re:Same Story in Germany by Shadow99_1 · · Score: 1

      Like the other poster mentioned, we actually have tried remote access for that CEO. In fact right before the conversation I mentioned above. He hated the experience and he certainly didn't feel it meet his needs. We do not have an in house development team (they outsourced it ages ago), so we don't have someone to make a custom app for the Ipads just to get this to work reliably. Using the existing apps we had considerable problems getting it to look like it's just an app (and so not confuse him) and the performance sucked. It also had major issues accepting touch input in a reliable fashion.

      If you would like to deal with a normal load of issues with a staff of four and try to play with stupid ipad apps to get this to work be my guest. I on the other hand would rather they just rewrite the stupid web app and be done with it.

      --
      we are all invisible unless we choose otherwise
    11. Re:Same Story in Germany by RollingThunder · · Score: 1

      IETab just runs IE; if your application is bloody-minded about only allowing in IE6, then Firefox plus IETab running IE8 will still get bounced.

    12. Re:Same Story in Germany by Billly+Gates · · Score: 1

      No that is not fine.

      The proper procedure is to tell the CEO in a business like way that his infrastructure is old and not competitive in today's encironment. I can get it to run on your IPAD as well as modern desktops and Andriod phones if we spend X to upgrade our POS intranet apps and deploy Windows 7 and IE 9.

      In return security will improve and the risk of the company's infrastructure failing will greatly be reduced.

      It is good the CEO sees how arcane and ancient it is. He has no clue at all how bad it is and that no one uses XP anymore outside of work and nursing homes. This will be a great opportunity to finely go around the PHBs and bean counters. He can then enjoy his new IPAD.

    13. Re:Same Story in Germany by archen · · Score: 1

      It's even crazier when they then want some ancient IE6 based web app to miraculously work on their shiny new Ipads and don't understand that they simply won't work. I have had a a CEO complain that we need to put IE6 on his Ipad because he needs to run X web app that was made 15 years ago and only works in IE6. He refused to accept that an Ipad will not run IE6, to the point where he even cursed at us and demanded we install Win XP on his Ipad to 'make it work'.

      I'm not a smug person, nor am I an Apple fanboy. But man do I enjoy how the ipad/iphone became the talk of the town and requires standards compliant HTML. For YEARS I advocated data agnostic solutions that used standards. I resisted the IE only solutions as much as possible, but inevitably management still overruled me because they wanted some BS solution. I also might add, that where there is smoke there is fire, and if it only works in IE, it's doubtful it will ever work well - even in IE.

      Now they all have shiny ipads / iphones, and their shit doesn't work with them. I rub this in as much as possible. Right now it's a prime time to make a lesson of this example that solutions need to be based off standards, NOT proprietary "only works with X". Train the corporate heads while you have the chance.

      "Sorry you could have used your sexy, trendy, expensive, cutting edge technology gadget with our system... except you didn't listen when I said some day you might need to use this on something other than IE. You remember right?... when you said, Well everyone uses IE, and only IE"

    14. Re:Same Story in Germany by jimicus · · Score: 1

      Tell me, how well does that work on an iPad?

  9. The US government isn't much better. by Anonymous Coward · · Score: 1

    The NSA still uses IE7 internally. Seriously, the NSA. These are the guys who are supposed to be on top of the information world.

    To be fair, the standard system image also includes Firefox 10 (that's new as of just a few weeks ago, it was 3.6 prior to that), but most of the people I have to work with use IE7 anyway.

  10. Meh -- Sort of by chill · · Score: 3, Interesting

    We still use IE6 in certain instances where I work (U.S. Gov't). It isn't part of a standard install, it is a published Citrix app and really only used for specific applications that require it. Our standard install is IE8 and Firefox 3.6.28.

    The problem isn't the cost of upgrading workstations. It is there are a couple of critical web-interface apps that require it and are an expensive bitch to upgrade. Older versions of Oracle Financials for one.

    --
    Learning HOW to think is more important than learning WHAT to think.
    1. Re:Meh -- Sort of by hendridm · · Score: 1

      It isn't part of a standard install, it is a published Citrix app and really only used for specific applications that require it.

      I know hindsight is 20/20, but I'm assuming modern RFPs require that the system be build so NOT to require a specific version of a specific browser? :)

    2. Re:Meh -- Sort of by Anonymous Coward · · Score: 0

      You have clearly never developed a web app. So Win 98 apps should magically still work on Win 7? Technology changes, apps gradually become outdated.

    3. Re:Meh -- Sort of by Billly+Gates · · Score: 1

      Its more profitable to target just one browser.

      Since IE is now released on an annual basis it would mean more forced upgrades for customers who want to be secure. It is a great benefit to have the app not work and check the version number on startup or during a connect.

      Whats the point if the customer pays for it and never upgrades again? You go out of business.

    4. Re:Meh -- Sort of by Anne+Thwacks · · Score: 1

      Technology only changes if you spend money. Spending money is currently out of fashion, especially in the UK government (Not having it is a good justification for not spending it. Perhaps someone should tell the Greeks).

      --
      Sent from my ASR33 using ASCII
    5. Re:Meh -- Sort of by drinkypoo · · Score: 1

      You have clearly never developed a web app. So Win 98 apps should magically still work on Win 7?

      Most of them do, if the developer made an effort to do things properly.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Meh -- Sort of by Danathar · · Score: 2

      Not sure why these things are called "Web App" when it's really an "IE APP".

      Hopefully (probably not) this will leave a bad enough taste in people's mouths NOT to create applications that only run on one vendor's browser and even worse one vendor's browser at a specific version.

    7. Re:Meh -- Sort of by chill · · Score: 1

      Yes and no. We actively avoid it, but sometimes they sneak in.

      For example, I still see occasional things bought that require a specific version of Java to work. "Sun JRE 5.1.2 - 5.2.4 only" type of stuff.

      From an end-user perspective, proprietary is evil. There is a potential for you to get left hanging so we really try and avoid it.

      --
      Learning HOW to think is more important than learning WHAT to think.
    8. Re:Meh -- Sort of by Anonymous Coward · · Score: 0

      Actually that sounds like a solution using the citrix solution to provide IE6 where needed, and upgrading the laptop/desktop to more modern browsers. It also reduces the attack cross section as the number of machines with the old software is reduced.

  11. The other side of the coin: by nuckfuts · · Score: 2

    Obviously sticking with IE6 is misguided, but I've seen the opposite side. I've worked in IT for 20+ years, and I've never seen any organization as cavalier about software upgrade costs as my provincial and federal governments. Entire departments would be upgraded to the latest version of Microsoft Office as soon as it came out. It had nothing to do with product features, or whether the previous version was sufficient for their needs. (And I'm not talking about file format changes, which caused a legitimate need for upgrading). The cost to taxpayers for unnecessary software upgrades must be be significant.

    1. Re:The other side of the coin: by Anonymous Coward · · Score: 0

      Well yeah, but modern browsers don't cost anything. And they even work in XP.

    2. Re:The other side of the coin: by parlancex · · Score: 1

      Governments often do not purchase software licenses from Microsoft through the same retail channels as businesses or home users, instead they usually have negotiated licensing agreement that entitles them to the latest version of certain CALs and common software suites under a specified annual cost. There isn't necessarily a cost for the upgrade, especially for products like Microsoft Office.

      Here in Alberta, our provincial government has a licensing agreement for K-12 education that includes Office. However, even if they didn't, there are probably a lot of reasons that end users aren't aware of that are important.

      Just a few examples:

      • Product support and security updates
      • Enhanced configuration management through more robust GPOs
      • Enhanced security through updated protocols for Exchange that require encryption
      • Compatibility with our also recently upgraded Exchange server which was upgraded to support more robust SPAM and malware filtering, as well as Unified Communications features
    3. Re:The other side of the coin: by nuckfuts · · Score: 1

      Yes, Microsoft licensing can include "software assurance", which entitles the buyer to upgrades as they become available, but such licences do cost more up front. In addition, this doesn't cover the manpower costs of installing the new versions on every computer, and the productivity loss when nearly every government worker at a computer is suddenly wondering "where the hell has my Print button gone?".

    4. Re:The other side of the coin: by Anonymous Coward · · Score: 0

      are you sure they are paying to upgrade? The licensing at my company covers os plus office, and it can be windows xp/windows 7 with office 2003/2007/2010, no difference in cost.

      http://www.microsoft.com/en-us/download/details.aspx?id=14452

  12. Blame shit web applications by benjfowler · · Score: 4, Insightful

    The culprit here isn't the desktops, it's the general, rock bottom, dire state of "enterprise" software.

    Truth be told, shrink wrap software is way better put together than the overpriced, utter shite corporate web apps that many government and big corporate users are forced to endure. They are usually written by inexperienced or bored 9-to-5 developers, and get bit-rotten and unmaintainable fast and thus are sheer hell to work on or upgrade.

    As a bored corporate drone myself, I feel the pain. I endure IE6 for using our business apps, and use Chrome for everything else.

  13. IE 6 works fine by Anonymous Coward · · Score: 0

    According to the CFO and all the accountants who make IT decisions, who are not actually IT people, CNN, MSBNC, Yahoo, Cisco Client Connect, ADP, Bank of America, and every work related site works with IE 6. Their apps work with IE 6.

    Why take risk and invest in something they already have that works fine?

    If it doesn't increase the share price then why upgrade?

  14. and hospitals by Anonymous Coward · · Score: 0

    Electronic Imaging Systems, for MRI's and the like... still require the archaic IE6 ...
    it seems idiotic programmers coded specifically for THAT browser and had no foresight...
    then again medical hardware is meant to be replaced often so our healthcare costs can keep skyrocketing...

    *end rant*

  15. Code to interfaces, test on implementations by MtHuurne · · Score: 1

    It's not that hard to make a web app that is future proof, as long as you write it to comply with the specs from W3C. I have developed a web app, so I know that not everything is specified unambiguously and not all browsers follow the spec to the letter, but it yields much better results than coding to one specific browser version.

    In our web app, over a period of about 5 years, the only regression on a browser upgrade I can recall is that IE8 would misrender VML. The very use of VML was a forced deviation from the specs because IE7 and 8 didn't support SVG (and while there is a VML spec, IE doesn't follow it).

    Back when these IE6-only applications were developed it was already clear that they would never run in non-Microsoft browsers. To me, that made it a bad idea, but many people didn't care or even realize that there were platforms other than Microsoft's. What people (me included) didn't realize though, is that even later IE versions would be incompatible with IE6.

    1. Re:Code to interfaces, test on implementations by Anonymous Coward · · Score: 0

      What people (me included) didn't realize though, is that even later IE versions would be incompatible with IE6.

      ASP .NET is the killer. The first thing that comes to mind is that in Jamaica there are actually A nal S eeking P arasites so ASP can mean many things to many people but by and large with the ubiquitousness of it within government IT it is truly a PITAsp. Or to quote Raiders of the Lost Ark
      "ASPs.....VERY dangerous...you go first!"

      IE 6 and XP and ActiveX associated with the original .net framework were essentially a complete vendor lock in device created by Microsoft. Some think that Microsoft did this in vengeance because of the anti-trust rulings. Here at Slashdot we all saw what they were really up to at the time and screamed bloody murder about it.

      Fact is that XP mode on the intranet server is the only thing that can possibly save MSFT them from themselves, and if you think about it you can see that their incredible vendor lock in tactics were and are flawless.

      The usage of non standard web coding in government and business will not stop any time soon. In reality until Microsoft is taken down a notch and they loose the stranglehold that they have on the industry there is not too much that can be done to rid ourselves of IE 6 coded web apps. Face it they have subverted html web tech then polluted it to such an extent that it has become impossible to get rid of IE6 and ActiveX.

  16. So does that large US phone company by Anonymous Coward · · Score: 1

    Their customer support reps use it. Apparently they have an ActiveX widget that only works on ie6. Sucks to develop other web apps for their use.

    Shouldn't name them, but if u are reading this please upgrade.

  17. Scary thing about all this by Anonymous Coward · · Score: 0

    I have been a patient in two hospitals here in Regina Saskatchewan (Canada) the last couple of months and I've noticed all the desktops still run Windows XP (even with the screensaver saying proudly windows xp) and IE 6.... scares the hell out of me when hospitals are even running old software like that and what looks like some kind of application they use with username/passwords to access/modify patient records and whatever else etc.

    1. Re:Scary thing about all this by Billly+Gates · · Score: 1

      The reasoning for this is they need to be certified for medical use. It takes *YEARS* to be certified. Once certified hospitals like to keep their investment around for a long time at least 5 years.

      I upgrades a hospital last year and they just got certified to run IE 7! IE 8 was still being tested. Hospitals have many legacy devices that all send things like PDFs of xrays, lab reports, and other things accessible by IE and Exchange 2003. They do not integrate well with modern standards. Not to mention are very very expensive so why upgrade?

      Biomedical equipment can't crash as lives would be at stake.

    2. Re:Scary thing about all this by Suferick · · Score: 1

      Even scarier: I visited a hospital recently where the desktops are still Windows 2000

    3. Re:Scary thing about all this by Anonymous Coward · · Score: 0

      Even scarier: I visited a hospital recently where the desktops are still Windows 2000

      Sorry if this comes across a bit 4 Yorkshiremen but Windows 2000? Luxury.

      I've only just managed to offload tech support for a pair of NT4 machines that are essential for running some bloody expensive lab kit. Unfortunately (for the company who have just undercut me and relieved me of this thankful task - note to anyone, if you don't want a job, quote HIGH) I actually worked with NT4 and the pimple-faced youths in this new organisation were in pre-school when it was killed off by 2k.

    4. Re:Scary thing about all this by Anonymous Coward · · Score: 0

      The reasoning for this is they need to be certified for medical use. It takes *YEARS* to be certified. Once certified hospitals like to keep their investment around for a long time at least 5 years.

      I upgrades a hospital last year and they just got certified to run IE 7! IE 8 was still being tested. Hospitals have many legacy devices that all send things like PDFs of xrays, lab reports, and other things accessible by IE and Exchange 2003. They do not integrate well with modern standards. Not to mention are very very expensive so why upgrade?

      Biomedical equipment can't crash as lives would be at stake.

      Bullfrogs and BS...Most pacs systems run a UNIX variant, from which the image data is then imported into the Windows based business servers. The imaging machines themselves do not run on an NT kernel except in Hospitals that were stupid enough to buy Compact NT back in the day when Sun, GE and Siemens ruled the roost. In fact a good many pacs systems run on RedHat and still have their core work stations running an embedded Unix or Linux based OS.

      The hospitals that spent big on NT mostly ran out and bought either HP or Sun Unix after realising that sending huge digital image output to an intranet rather than shooting things directly to an Xray printer with Windows NT controlled equipment was almost like being constipated for a month!

      The office part of the Hospital is where you find MSFT servers ...... Take a trip to Cerner in Kansas City and learn how they make their mega bucks integrating pacs images into a Windows environment by hacking away at MS SQL and .NET ...heck they even churn out VB script by the cartload and make a killing doing it!

  18. It's about stability by Anonymous Coward · · Score: 0

    A lot of people bitch about IE6 but the fact is it was a stable platform to build web apps to; There is no real equivalent even now - FF, Chrome, even Opera change the way things are done each major, and sometimes even minor, version bump which means it is very difficult to take advantage of the more niche or esoteric functions that claim to support.

    IE6 is one of the longest running web browsers and that meant it was stable target for bespoke apps which government and corps often run a lot of. It sucked, yes, but that API (or whatever the correct term is) stability counts for a lot.

    As a case in point, the web-based MIS that some schools here use was originally targeted at IE6 but as browser features evolved (JIT in particular), the schools demanded that Firefox was supported as it was two orders of magnitude faster. However, every time Firefox upgraded it would break something and the schools would end up going back to using IE6 for a few weeks to work around the broken parts until the problem could be identified and fixed by the MIS company.

    The problem at the moment is that the HTML5 standards implementation is diverging - Firefox, Opera, IE8/9, Chrome, Safari etc. all do it slightly differently, enough so that you can't rely on anything but the most central parts of it. Hell, even well-featured HTML4 will render slightly differently in all the different browsers; I'm not even sure HTML3 would render similarly in different browsers.

    It's a mess. Whereas before you just needed to target IE or Netscape (Ignoring us Opera users...) you now have a myriad of platforms. I thought we'd seen the last of the "Designed for Netscape/IE/Moomoomoo" labels but it seems they are coming back.

    The sad and ironic thing is that Flash is the one stable platform common to all browsers right now...

  19. The truth is brutal. by Anonymous Coward · · Score: 0

    It's because government IT staff is lazy, doesn't catch up with latest tech, as well directors doesn't see the need as well. They are just poor and low-class of our society running IE6, when everybody else migrated to iPads, Windows 7 and OS X.
    Learning new things is just above them; face it, don't try to conceptualize it and make stories on the level of 5 year old lying kid.
    You are running IE6 -> You are stupid like the least 5% of population. That's it. Don't try to explain it, it makes you look even dumber.
    Upgrades are essential in supporting IT. If you don't do this, your support is a lie.

  20. an important note by slashmydots · · Score: 1

    Everyone states things like "4% of internet traffic is still IE6. WHAT IDIOTS?!" Yeeeeah, that's me downloading drivers on a reinstall. It ships by default with XP so it won't be gone from server logs until after April 8th, 2014. Also, technically if a place was using Deep Freeze, it would be downgraded from moronic to unwise because security issues would be as critical.

  21. Not entirely MS fault. by DarthVain · · Score: 1

    I have to keep IE6 around because we have a ton of corporate apps that work on nothing but. I don't chalk that up to MS fault, but poor development. Transition should be interesting.