Slashdot Mirror


Microsoft To Drop Support For Older Versions of Internet Explorer

An anonymous reader writes After January 12, 2016, only the most recent version of Internet Explorer available for a supported operating system will receive technical support and security updates. For example, customers using Internet Explorer 8, 9, or 10 on Windows 7 SP1 should migrate to Internet Explorer 11 to continue receiving security updates and technical support. From the blog post: "Microsoft recommends enabling automatic updates to ensure an up-to-date computing experience—including the latest version of Internet Explorer—and most consumers use automatic updates today. Commercial customers are encouraged to test and accept updates quickly, especially security updates. Regular updates provide significant benefits, such as decreased security risk and increased reliability, and Windows Update can automatically install updates for Internet Explorer and Windows."

138 comments

  1. Only 17 months to go... by CaptQuark · · Score: 2

    Are they really suggesting that IE 11 will still be the most recent version in 17 months.... ?

    1. Re:Only 17 months to go... by kolbe · · Score: 5, Insightful

      The problem I have is that IE11+ is such a PITA and it is difficult to get working with various Enterprise Java applications without disabling Protected Mode and completely unsecuring it or setting custom registry keys/policies. EMC Unisphere, various Cisco apps like UCSM and Fabric Manager... Even several recent Oracle tools just gag on IE11+ without spending hours configuring it to work every time you launch it.

      Well, all the more reason to dump it altogether.

    2. Re:Only 17 months to go... by Anonymous Coward · · Score: 0

      Only 17 months to go

      Only 13 years late to the party. Anyone with sense dropped support for Internet Explorer when IE6 was released.

      Coincidentally, its birthday is a little over two weeks away, if anyone wants to wear black.

    3. Re:Only 17 months to go... by Z00L00K · · Score: 4, Insightful

      Not even some of Microsofts own services (Outlook web mail for example) works well with IE11 - they work with Opera or Firefox though, so something is broken in IE11.

      Many major companies also rely heavily on older versions of IE and outright prohibits other than the approved version through scripts instead of making sure that they are conformant with web standards using HTML and CSS validators. Of course - if there's Javascript involved then it's necessary to test with more than one browser since there's no good Javascript validator around ensuring portable code.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    4. Re:Only 17 months to go... by cbhacking · · Score: 3, Insightful

      Since there's already a pre-release version of IE12, probably not! They've increased the release rate a good bit the last few years; Win7 shipped with IE8. Still nowhere near as fast as Firefox and Chrome bump their "major" version numbers these days, of course, but that's no surprise.

      --
      There's no place I could be, since I've found Serenity...
    5. Re:Only 17 months to go... by Anonymous Coward · · Score: 0

      Yeah, anyone with sense dropped support for the browser that still seems to be the de facto standard for all the companies that I have worked for these last ten years. One the other hand, those without sense earn their living.

    6. Re:Only 17 months to go... by Anonymous Coward · · Score: 0

      Your problem is not IE, it's the fact you depend on Java. Java in the browser is broken beyond repair to the point where no browser vendor wants to enable it by default. And that's a smart thing to do.

    7. Re:Only 17 months to go... by _merlin · · Score: 5, Interesting

      From my experience so far, IE11 with default settings renders far more like Firefox/Safari than any prior version of IE. A lot of the brokenness probably comes down to web apps detecting IE, then serving content designed for old, broken IE. When new, standards-compliant IE becomes more widespread, people can just remove the code for supporting bad old IE altogether.

    8. Re:Only 17 months to go... by znrt · · Score: 1

      Many major companies also rely heavily on older versions of IE

      some people just don't learn.

    9. Re:Only 17 months to go... by Anonymous Coward · · Score: 0

      Not even some of Microsofts own services (Outlook web mail for example) works well with IE11 - they work with Opera or Firefox though, so something is broken in IE11.

      Many major companies also rely heavily on older versions of IE and outright prohibits other than the approved version through scripts instead of making sure that they are conformant with web standards using HTML and CSS validators. Of course - if there's Javascript involved then it's necessary to test with more than one browser since there's no good Javascript validator around ensuring portable code.

      Is this a really old version of Outlook web mail? Because to me IE11 seems to not only run OWA just as good as Firefox, but it runs by far most sites just like FireFox (it even identifies as FF for this reason, on sites that do IE-sniffing you will get their FireFox-version in IE11).

    10. Re:Only 17 months to go... by Lonewolf666 · · Score: 1

      I recently had a similar problem with Microsoft Test Manager. With IE11 the content of the administration web page was not visible. I could not find the reason in the security settings (and accessing the web page from the same system suggests that it should be a "trusted zone"). Firefox 31 did the job though.

      So I suspect this was another case of IE11 being broken for a Microsoft service.

      --
      C - the footgun of programming languages
    11. Re:Only 17 months to go... by mpe · · Score: 1

      From my experience so far, IE11 with default settings renders far more like Firefox/Safari than any prior version of IE. A lot of the brokenness probably comes down to web apps detecting IE, then serving content designed for old, broken IE. When new, standards-compliant IE becomes more widespread, people can just remove the code for supporting bad old IE altogether.

      Or they could fix the broken version detection code, so that it only does that with actually "broken" versions of IE.

    12. Re:Only 17 months to go... by Anonymous Coward · · Score: 4, Insightful

      From my experience so far, IE11 with default settings renders far more like Firefox/Safari than any prior version of IE. A lot of the brokenness probably comes down to web apps detecting IE, then serving content designed for old, broken IE. When new, standards-compliant IE becomes more widespread, people can just remove the code for supporting bad old IE altogether.

      Or they could fix the broken version detection code, so that it only does that with actually "broken" versions of IE.

      You're describing the fundamental problem with browser detection -- when you write it, you don't know how it will work with future browser versions.

      If you deploy browser detection code, you *must* take responsibility for contantly re-testing it against every new browser that gets released. That's not easy to do in practice, and nobody actually manages to do it (or remembers to do it, or even realises that the need to do it), and thus we still have sites that break whenever a new version of IE comes out, or whatever other browser that falls foul of their detection code.

      And that is why browser detection is bad practice. It puts an additional burden on you for ongoing support.

    13. Re:Only 17 months to go... by Z00L00K · · Score: 1

      And interestingly enough - setting IE11 to compatibility mode doesn't resolve the issues I have seen.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    14. Re:Only 17 months to go... by grahamm · · Score: 1

      Yes, if you want to run java, run it as a standalone app not in the browser.

    15. Re:Only 17 months to go... by Anonymous Coward · · Score: 0

      Had to add *.microsoft.com to the compatibility list (update.microsoft.com was not enough) to get the MS Update install page to work, otherwise it tells me to open the control panel to install updates which I already did and clicked the link to switch to MS-Update. (I couldn't even find this bug listed in all but few scattered forum posts after a few hours of searching)

      Switching to MS Update has got to be the only thing left I ever use IE for and only when installing Windows 7, At least until they have a way to turn this on without visiting the page. (then I just might just remove it completely...)

    16. Re:Only 17 months to go... by CaptnZilog · · Score: 1

      Wait... MS is going to start actually supporting IE now?!? Will it actually properly implement the HTML standards now??
      It's about time. :D

    17. Re:Only 17 months to go... by satuon · · Score: 2

      If that's so, then why not switch to Firefox or Chrome? Wasn't the whole reason to use IE that some sites will not render properly/refuse to work otherwise?

    18. Re:Only 17 months to go... by Anonymous Coward · · Score: 0

      In other words, IE 11 bears a closer resemblance to browsers that don't suck than older versions of IE.

    19. Re:Only 17 months to go... by _merlin · · Score: 4, Insightful

      Competition's never a bad thing. I'll take three viable web browsers over two. No-one wants to go back to the days of sites targeting specific browsers. "Best experienced with Netscape" - screw that.

    20. Re:Only 17 months to go... by Bing+Tsher+E · · Score: 1

      No browser properly implements the Markup Language. Further, too many people think they are 'developers' because they coded some little scripts inside the marked up document. Or some big ugly script, frighteningly.

    21. Re:Only 17 months to go... by dannydawg5 · · Score: 4, Informative

      The latest version of IE does not send "MSIE" in the user agent. Microsoft did this intentionally to encourage feature detection instead of browser detection. Most detection code relies on "MSIE" being present.

      If you must, it is still easy to catch IE though. "Trident" is still present.

    22. Re: Only 17 months to go... by Anonymous Coward · · Score: 0

      You are conflating the word "must" with "should" or "could" or "might consider"!

    23. Re:Only 17 months to go... by Hamsterdan · · Score: 1, Insightful

      "If you deploy browser detection code, you *must* take responsibility for contantly re-testing it against every new browser that gets released. "

      So, every 2 days for Firefox?

      --
      I've got better things to do tonight than die.
    24. Re:Only 17 months to go... by Anonymous Coward · · Score: 0

      What's your compelling reason to switch if IE11 is (more) standards compliant?

    25. Re:Only 17 months to go... by Deathlizard · · Score: 1

      When new, standards-compliant IE becomes more widespread, people can just remove the code for supporting bad old IE altogether.

      No they can't because they never Kill old IE. Even on their life cycle chart, they are supporting 3 Different Versions of IE, so devs have to code for the lowest common denominator (IE9) or force users away from IE altogether. Chances are it's going to get worse once Windows 7 goes into extended support and they quit updating IE for it as well.

      They need to Support 1 IE Version across all supported mainstream and extended platforms. If they did that instead of using IE as some BS Excuse to get people to Upgrade Windows, maybe they wouldn't bleed so much browser market share.

    26. Re:Only 17 months to go... by tepples · · Score: 1

      To leave open the option of not having to buy a Windows license for machines that don't run much other than a browser and LibreOffice.

    27. Re:Only 17 months to go... by Mondor · · Score: 1

      No, they are saying, that the most recent version will be supported. If it will be MSIE 13, then 11 and 12 won't be supported anymore. Isn't it the same with, say, Chrome? Just asking.

    28. Re:Only 17 months to go... by Anonymous Coward · · Score: 0

      Your grandpa called. He wants his joke back.

    29. Re:Only 17 months to go... by Anonymous Coward · · Score: 2, Insightful

      IE11 does not support CSS conditionals *at all*. That is what people have used for many years to include additional CSS containing hacks for older IE with inferior CSS support.

      This breaks my head. In IE9 and IE10, for example, there are render modes you can use to test content in older versions of the browsers. It wasn't completely perfect but it was 99%, and good enough for me not to have to run VMs with older IEs to do all of my IE testing. IE11 though - it still has support to view content in an older rendering mode, but without the CSS conditional support, it's close to worthless for any site that uses those conditionals to apply CSS fixes, which is most all of them.

      Progress.

    30. Re:Only 17 months to go... by Anonymous Coward · · Score: 0

      Let your Exchange admins know they are out of support then. Exchange 2010 SP3 supports IE11:
      http://support.microsoft.com/kb/2866064

      SP2's support ended 4/8/2014
      http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=Microsoft+Exchange+Server+2010&Filter=FilterNO

    31. Re:Only 17 months to go... by gander666 · · Score: 1

      Great, now will I no longer be able to use a supported browser as well as be forced to use a deprecated, and highly insecure version of Java to do my job (which involves far too much Oracle fluffery.

      The fact that Oracle applications demand IE at all is quite ironic...

      --
      Suppose you were an idiot and suppose you were a member of Congress ... but I repeat myself. - Mark T
    32. Re:Only 17 months to go... by Wycliffe · · Score: 1

      I agree with this. 3-5 is probably the sweet spot. Any more and developers are going to start slacking and not test all the
      browsers. Unfortunately we have 3-5 browsers and then a dozen different versions of each. This move by microsoft
      is a move in the right direction. Web developers shouldn't be expected to support 6 different versions of IE and 6 different
      versions of firefox. After 3 years you should probably get a security warning every time you open your browser
      telling you that your web browser is obsolete and making you click an "i understand that the web will be broken if I continue"
      button before continuing.

    33. Re:Only 17 months to go... by Anonymous Coward · · Score: 0

      I've actually come up with a good use-case where browser detection is valid. More accurately, platform detection is needed.

      Right now, video is a mess. You either use shitty Flash FLV, or you detect the browser/platform and serve up something non-shitty.

      For in-browser "streaming" (but not really) video (using embed, object, or HTML5 video tags), you have to detect the browser itself, and specifically the rendering engine. Then you have to feed the correct video format to each browser. Anymore, just about all browsers will work with h264 in an MP4 container. Some of them (primarily Chrome) will also accept VP8 in WebM. Any browser on Windows can probably handle WMV, either directly or by handing it off to Windows Media Player.

      For streaming network video, it's a lot more complicated. Usually buffering and latency are an issue if you're using these. Windows prefers ASF muxing with just about any codec over HTTP or WMSP. RTP and RTSP require third-party player software (VLC is recommended). MacOS and iOS prefer MP4 muxing with MPEG4 codecs, and they pretty much hate every streaming protocol that isn't AirPlay. You can get by with RT(S)P, but barely, and only because RTSP/RTP is part of how AirPlay does its thing. Android prefers MPEG muxing with MPEG2 codecs (no, not WebM/VP8!) over HTTP. Linux works with just about anything because it has to and can. Linux also has an abundance of tools for controlling, viewing, transcoding, sending, receiving, listening for, and serving streaming video.

      So when you're building a page that has a link to a video or video stream (an rtp:// protocol link is perfectly valid in an href), you need a reliable way to serve the correct (i.e. working and functional) file or link to the client. That raises a need to detect either the browser or the platform or both.

    34. Re:Only 17 months to go... by Anonymous Coward · · Score: 0

      Yes, it is progress, since using those dumbass conditionals is idiotic. Youre complaining that you wont have to do that shit any more?

    35. Re:Only 17 months to go... by Yunzil · · Score: 1

      it is difficult to get working with various Enterprise Java applications without disabling Protected Mode and completely unsecuring it

      Wait, are you complaining IE is too secure?

    36. Re:Only 17 months to go... by david_thornley · · Score: 1

      IE 5 and 6 were, when introduced, very good browsers by the standards of the time, and often better at standards conformance than their rivals (or rival). Having produced a better browser than Netscape could, Microsoft dominated the field and stopped improving. By the time people started moving away from IE6, IE6 was an embarrassing and insecure dinosaur, and Microsoft has played catch-up ever since (well, ever since they got off their metaphorical ass anyway).

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    37. Re:Only 17 months to go... by david_thornley · · Score: 1

      It's worse than that. Most non-IE browsers nowadays have pretty similar rendering engines. IE isn't a WebKit-derived browser, and it's useful to have it out there competing.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  2. they might as well by FudRucker · · Score: 2, Insightful

    since they have not been able to secure Internet Explorer at all for years when they did claim to maintain and have support for it

    http://en.wikipedia.org/wiki/C...

    --
    Politics is Treachery, Religion is Brainwashing
    1. Re:they might as well by Anonymous Coward · · Score: 0

      good, do what the other vendors do and only have one supported version

    2. Re:they might as well by LordLimecat · · Score: 2, Informative

      Wow, using a 15 day old build of firefox to assert that IE is terribly insecure (because it has an unpatched vuln).

      Of course, you couldnt have made this post 15 days ago, because the score would have been "1 unpatched for IE11, 11 unpatched for mozilla"

      IE isnt the greatest security-wise, but Id probably trust it over Firefox these days.

    3. Re:they might as well by Anonymous Coward · · Score: 0

      I'm willing to forget the security aspect and would be happy if the bloody thing rendered properly! I spent yeeeears playing devils advocate and defending them, but was sick in my own mouth when I kept tripping over stupid bugs in 11

      IE is dead to me.

      Microsoft, just give it up and adopt WebKit like everyone else... seriously, you lot just don't have what it takes in the browser department

    4. Re:they might as well by Art3x · · Score: 4, Informative

      "Unsupported" is the magic word to get huge companies like mine to at last move on. I can't tell you how happy that will make me, an intranet programmer, if my company's official browser is IE 11 or something.

      Right now it's 8. It and 7 were wonderful improvements in CSS from IE 6, which our official browser until just a few years ago. I fought with IE 6 for years and it felt like it would it never quite go away. I know that there are some poor souls in the world still using IE 6, but since it's no longer our company's official browser, I don't have to think about it. The thing that made my company finally upgrade was because a vendor forced them to, saying that their web app would no longer work in IE 6.

      While IE 7 and 8 brought real improvements in CSS support, JavaScript is quirky until at least 9. Microsoft's unpredictable implementation of JavaScript is part of the reason JavaScript has a shady reputation. If Chrome, Firefox, Opera, and Safari were the only browsers I had to write against, it would have been a different life.

    5. Re:they might as well by Z00L00K · · Score: 1

      If you can make IE work that is - today it doesn't even work well with M$ services.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    6. Re:they might as well by mpe · · Score: 1

      If you can make IE work that is - today it doesn't even work well with M$ services.

      Using IE8 or IE9 often appears to be an effective workaround here. For some reason webmail appears especially troublesome with IE10 and IE11.

    7. Re:they might as well by Bogtha · · Score: 1

      Right now it's 8. It and 7 were wonderful improvements in CSS from IE 6

      Not really. The only real difference between 6 and 7 from a CSS perspective was a few extra selectors and bug fixes. The real improvements came with version 8, which finally had full support for CSS 2.

      --
      Bogtha Bogtha Bogtha
    8. Re:they might as well by Bing+Tsher+E · · Score: 1

      Webmail?

      pop.google.com works great for me. I never even see any ads.

    9. Re:they might as well by operagost · · Score: 1

      Anyone using IE6 has bigger problems, because their OS isn't even supported. No desktop version newer than XP supports IE6.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    10. Re:they might as well by Daniel+Hoffmann · · Score: 1

      It is even worse for vendors, In companies that sells services and products for other companies you have to use the lowest common multiple which was IE6 until a couple of years ago, now it is IE8.

      You are also absolutely right about your points for IE9, I had to fight with my bosses for our new product to be >= IE9 only. They wanted the latests HTML5 buzzwords but also to be able to run on old IE. The alternative was building everything using Java Applets...

    11. Re:they might as well by LordLimecat · · Score: 1

      Hows that Mozilla Kool-Aid taste?

      You want security, use Opera, Safari, Chrome, anything-- but Mozilla is a disaster.

    12. Re:they might as well by david_thornley · · Score: 1

      Does Windows 7 support IE 6 in XP compatibility mode?

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    13. Re:they might as well by cbhacking · · Score: 1

      Yes (in the sense that the XP Compatibility Mode image comes with IE6 installed), but also no (in the sense that XP in general is no longer supported).

      --
      There's no place I could be, since I've found Serenity...
  3. Oh Boy! by TWX · · Score: 1

    Firefox will have some competition for version numbering again!

    --
    Do not look into laser with remaining eye.
    1. Re:Oh Boy! by Anonymous Coward · · Score: 0

      I don't have a problem with fast releases and big version numbers as long as they're automated or easy to deploy. 'Foobar 123' is no harder to remember and/or migrate to than 'Foobar v1.2.3'.

      If your complaint was about changes to the UI, functionality, the number of security patches needed every week, or the shifting target for add-on development...

    2. Re:Oh Boy! by Anonymous Coward · · Score: 0

      Written on Firefox version 736280482672103482.1

    3. Re:Oh Boy! by Teun · · Score: 1
      Exactly, numbers are just that, numbers.

      As long as the functionality is there I couldn't care less if they changed to an AA, AB, AC etc. scheme.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    4. Re:Oh Boy! by sound+vision · · Score: 1

      If you can't see the benefit of sensible version number system, I must infer you haven't done any development or serious IT work. Although it shouldn't be very hard to see the benefits as a "power user" either, which is sort of my minimum expectation for Slashdot.

    5. Re:Oh Boy! by Teun · · Score: 1
      Come on! As long as the numbering is sequential it makes no difference.

      Incompatibilities aren't recognisable by their number.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    6. Re:Oh Boy! by I'm+New+Around+Here · · Score: 1

      It makes no difference to the end user. But it makes a big difference to corporations that decide what software to allow on computers. Or what software their product supports or works with.

      Even the various Linux flavors keep a 'long-term' version of their os, just so businesses know they can count on that version for more than a month or half-year.

      --
      If you think I voted for Trump because of this post, you're wrong. I voted for Dr. Jill Stein of the Green Party. Again.
    7. Re:Oh Boy! by Teun · · Score: 1
      For allowing certain versions it's just a matter of setting a range but this would not help if that range is no longer maintained.

      The "Mozilla Firefox Extended Support Release" is one solution to the problem, others publishing serious software should do similar.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    8. Re:Oh Boy! by TWX · · Score: 1

      Yep.

      Usually the X. number is a family of related versions, and sometimes the #.X is also a family of related versions. When this is used it's much easier to know to support all of X.# or Y.X.# because of similarity. To apply this to Firefox specifically, 29-31 would be one X.X.# or X.# if grouped logically.

      --
      Do not look into laser with remaining eye.
  4. Corp IT that can't seem to follow. by Anonymous Coward · · Score: 2, Interesting

    I for one welcome this. I work in a company that up till a few months ago was still on IE8. They upgraded to IE10 instead of going directly to IE11 which is totally insane in my mind and the reasoning by the folks doing the deployment was to use stable and tested.

    This same company still uses to this day a version of Java that is both old and recommended by Oracle to update immediately because it has critical vulnerabilities which is even more insane to me when you factor in that they work with so much customer data breaches and the potential for lawsuits just seems extremely high.

    1. Re:Corp IT that can't seem to follow. by mjwx · · Score: 4, Insightful

      I for one welcome this. I work in a company that up till a few months ago was still on IE8. They upgraded to IE10 instead of going directly to IE11 which is totally insane in my mind and the reasoning by the folks doing the deployment was to use stable and tested.

      This same company still uses to this day a version of Java that is both old and recommended by Oracle to update immediately because it has critical vulnerabilities which is even more insane to me when you factor in that they work with so much customer data breaches and the potential for lawsuits just seems extremely high.

      As a sysadmin, running the current version -1 is the safe bet for most businesses. The problem is that few businesses have an upgrade path, policy or methodology so you end up being current version -2 or -3 because no-one is willing to sign off on an upgrade.

      Its not that we dont want to upgrade, its that management dont want any disruption to anything. So they refuse to allow upgrades until eventually the manufacturer forces the issue (and sometimes not even then). As for running out of date versions of Java (or anything else) it's always due to one legacy application that relies on that version and that version only. Its always a critical application that was written by some rock star developer a few years ago and since that developer left a few years ago no-one know how it works or how to upgrade it to function with a more current version of Java. Whenever I hear a developer say "oh, I can write a little application to do that" for an important process or requirement I want to beat them to death with a rusty pipe.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    2. Re:Corp IT that can't seem to follow. by Anonymous Coward · · Score: 0

      When I get around to deploy an update of Java in our company (I'd like to do it every time but sometimes I can't make it), I simply remove all older versions of Java and only install the latest version on our office PCs. The servers are a different matter. But if a Java Applet somewhere in the WWW doesn't work with the latest version of Java, it's simply broken and should be fixed.
      It's the same with web applications. We install IE 11. They should get it to work with IE 11 or its compatibility mode.

      And I have yet to find a website, that can't be used with IE 11, or a Java App that has to use an older version of Java and is critical for our business. But if all else would fail, I would downgrade IE or Java or install Firefox. Because the computers are there to get work done, not for me to have them running cutting edge versions of all software products.

      We also install Microsoft Updates right away. Most of the time without previously testing them. The only time this really hurt were the one time the antivirus patterns for Microsoft Endpoint Protection knocked out Windows XP. But I don't think many people test antivirus patterns before they get rolled out.

    3. Re:Corp IT that can't seem to follow. by Anonymous Coward · · Score: 0

      I'm the AC of the other comment of the company that does install IE 11. We or at least I believe that our company employs mostly responsible persons. So we try to protect our users from things from which we think they don't want to do to their PCs. But we don't lock them down. So, we roll out Windows Updates. But: they're neither hindered nor encouraged to manually install all the Windows Updates they want. So, by the time we rolled out IE 11 for the entire company, we already did know it was in use by 5-10 % on our computers in all departments of our company.

    4. Re:Corp IT that can't seem to follow. by mpe · · Score: 1

      As a sysadmin, running the current version -1 is the safe bet for most businesses. The problem is that few businesses have an upgrade path, policy or methodology so you end up being current version -2 or -3 because no-one is willing to sign off on an upgrade.
      Its not that we dont want to upgrade, its that management dont want any disruption to anything.


      Possibly also the managment does not want to spend the money on testing to ensure that any disruption is minimised. Especially when one "upgrade" can require all sorts of consequential changes. Be they upgrading something else or changing obscure settings to maintain the status quo.

      So they refuse to allow upgrades until eventually the manufacturer forces the issue (and sometimes not even then). As for running out of date versions of Java (or anything else) it's always due to one legacy application that relies on that version and that version only. Its always a critical application that was written by some rock star developer a few years ago and since that developer left a few years ago no-one know how it works or how to upgrade it to function with a more current version of Java.

      They may not even be an inhouse developer. Though if they are an external vendor you might be left to guess that that is the most likely possibility. Or they no longer "support" your version, but their latest version requires you to make a major migration, but is very different from the current version anyway.

    5. Re:Corp IT that can't seem to follow. by DutchUncle · · Score: 1

      As a sysadmin, running the current version -1 is the safe bet for most businesses. The problem is that few businesses have an upgrade path, policy or methodology so you end up being current version -2 or -3 ...

      That tradition goes back to mainframes. One difference is that in the IBM mainframe days, a "version" came out every blue moon, thoroughly tested by an itty bitty monopoly, and justifying similar thorough testing by users; whereas today a "version" can arrive every few days (or faster for people who watch commits to the archive) and testing would almost be continuous.

  5. Re:don't you mean by Anonymous Coward · · Score: 0

    So it's your favorite browser?

  6. Just uninstall it! by Anonymous Coward · · Score: 0

    Except you can't uninstall it. "Because Internet Explorer is a Windows feature, you can't uninstall it, but you can turn it off. Here's how:"
    Gee, Thanks Microsoft!

    1. Re:Just uninstall it! by Anonymous Coward · · Score: 0

      Even if you turn it off, some Microsoft Apps will still start it simply because they have the path to the .exe hard coded inside them.

    2. Re:Just uninstall it! by Anonymous Coward · · Score: 1

      Oh baby, your hard code feels so good inside me.

  7. Cool by the_Bionic_lemming · · Score: 1

    Sounds like a great reason to not use Internet Explorer.

    In the past 7 years I've only had to use it a relatively few times - For instance Illinois gubment can't be bothered to make their apps non IE friendly.

    but hey, to each their own.

    --
    _ _ _ Go for the eyes Boo! GO FOR THE EYES!
  8. So latest only by Anonymous Coward · · Score: 0

    Up to this point, many companies have waited till 'we see if its broken or working' before they adopt the latest. Now they will be pressed to use the latest, and chance broken software (and dysfunctional business processes). I'm sure many of them are thrilled about that.

  9. This is sad by thieh · · Score: 1, Interesting

    On one hand, most businesses are locked into using Windows, and on the other hand, Microsoft are phasing out everything every now and then in order to force you to pay them to upgrade. On top of that businesses usually have draconian versions of stuff that won't run without equally draconian versions of Windows/Office/IE. I wonder how do people get into that spiral

    1. Re:This is sad by ron_ivi · · Score: 4, Insightful

      Sad? I'd say it's happy.

      So many big companies locked themselves in to "microsoft IE-6 only solutions" - and open source advocates have long cautioned them against depending too much on a vendor that might yank support whenever management changes or quarterly profits dictate yanking support to encourage upgrades.

      This will teach them a lesson they'll hopefully never forget; and look for cross platform solutions in the future.

    2. Re:This is sad by Mask · · Score: 1

      "This will teach them a lesson they'll hopefully never forget".

      Most individuals learn, not everybody. Some organizations learn, not all of them. Humanity almost always repeats past mistakes.

      The same forces that made people use the "IE-6 only solutions" will always exist. New MBAs and engineers will keep only these forces in mind and will not even consider the impact of their decision on the "potential" distant future. It is not that they will not be aware of the dangers, it is just that feeling the pain in person is not the same as the theoretical knowledge about pain.

  10. Support??? by pitchpipe · · Score: 5, Funny

    Microsoft supports Internet Explorer?! I wouldn't admit to it if I was them.

    --
    Look where all this talking got us, baby.
  11. Wait, what, huh? by jd · · Score: 0

    IE is supported? When did this happen?

    Last I heard, they reluctantly release updates when other parts of the OS beat them on bugs per kg of code. (They stopped measuring lines when someone googled the term.)

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:Wait, what, huh? by istartedi · · Score: 2

      bugs per kg of code

      That code is heavy, man /hippie.

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
  12. Hell No by Anonymous Coward · · Score: 1, Interesting

    There is a reason why nobody should "automatically" update Windows. It's an identical reason toy why you shouldn't let Linux or MacOS X update automatically.

    If the administrative account isn't used to confirm installing updates, then it will be compromised.

    Here's one example:

    After installing X product that shall remain nameless, suddenly Windows sees a need to push 20 updates or so. Ok whatevers. So those updates are installed, but now when I try to install Visual Studio and the SDK's they all fail. Now why is that? Maybe if I had installed Visual Studio and the SDK's first this wouldn't have happened. But nooo... Windows Update wants all the updates to be installed at that time. Some of the updates even fail, resulting in multiple reboots before they all install.

    Linux is nearly as bad, if not worse. Because of huge obnoxious chains of dependency in response to OSS developers fond of reinventing the wheel to circumvent licenses they don't ideologically agree with, I have to put up with things like OpenSSL being replaced by LibreSSL, or MySQL being replaced with MariaDB for no damn reason.

    MacOS X has the least obnoxious behavior, but the update window is much shorter. It does things right by confirming to install updates, but has to restart the OS for everything including iTunes, which shouldn't need an update if it's all user-space.

    The problem with the Microsoft Platform, is that MSIE is "integrated" into Windows in a way that will always be more dangerous than simply using Firefox or Chrome.This goes back to Windows 98SE and MSIE 4. The entire monopoly problem. Had the law people not interfered we might have been looking at a world of websites that only work with ActiveX apps (believe me, certain CRM software did this even as late as 2004, and I'm talking about you Siebel)

    Microsoft's screw up was integrating it. The only good that came out of that lawsuit was that Microsoft couldn't co-opt the XHTML or CSS standards with propietary extensions, and it likely drove off a lot more people from MSIE when other browsers ... oh wait I'm getting ahead of myself. There were no other browsers.

    Netscape's last version was 4. Mozilla restarted from scratch, Opera was still a pay browser, and nobody else put anything else worth a damn. It took APPLE to take KHTML and make Webkit to create a third browser. Everyone thank Apple for that, because if they didn't, Google Chrome would not exist, and no smartphone would exist either.

    1. Re:Hell No by jones_supa · · Score: 1

      I agree. While Windows generally works better than Linux on desktop these days, the update system in Windows is fucking flaky.

    2. Re:Hell No by Anonymous Coward · · Score: 0

      Last year I would have agreed that Chrome is a good thing although I'm not sure I would thank Apple for it. Lately, Google's megalomania is having a more noticeable impact in Chrome. Also, the quality is going downhill. It's locking up hard, becoming less responsive. I've been thinking of going back to Firefox as the alternative. IE wouldn't be so bad except that so much ill will built up that web devs abandoned it as soon as they could. Result? You needed to abadon IE just to navigate the web. Chrome's fast scripting pulled me that way, since everything insists on scripts these days. I'm not sure what's happening with Chrome development now; but it's definitely having issues. Then again, maybe the Fox is worse. I haven't tried it for a while. The only thing that has remained constant about browsers over the years is... change.

    3. Re:Hell No by Anonymous Coward · · Score: 0

      MacOS X ... has to restart the OS for everything including iTunes, which shouldn't need an update if it's all user-space.

      That's an exaggeration of actual behavior, to be certain. I cannot recall the last time OS X forced a restart for an iTunes update. System-level updates do force a restart, but userland refreshes do not.

  13. Customers using internet explorer by lusid1 · · Score: 1

    should upgrade to an operating system.

    1. Re:Customers using internet explorer by Z00L00K · · Score: 1

      I'd take a stable OS like OpenVMS then.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
  14. So are they going to fix the issues wtih IE ? by Malfuros+the+Wizard · · Score: 2

    IE 10 and IE 11 are significantly buggy and seem to have broken compatibility with older sites whereas FireFox and Chrome still work on those sites perfectly well. Of course Microsoft would say fix the site but when you are dealing with sites that provide services to your business stability is king, as a result we have managed to stop IE10/11 being deployed on any of the Win 7/Win XP machines in use. Microsoft dropping support for older browsers means we will stop using IE, we had already started installing Chrome for compatibility reasons, looks like its going to be chrome all the way. If Google and Mozilla can maintain a decent level of backwards compatibility why cannot Microsoft. Ties in with the decision to stick on Win 7 because Win 8/8.1 breaks some of our applications, there is no upgrade option on those applications, they were written eight years ago and they HAVE to keep working. Microsoft needs to realise the business community wants stability, they don't want shiny new UI's and whistles and bells.

    1. Re:So are they going to fix the issues wtih IE ? by Z00L00K · · Score: 1

      Microsoft IE11 isn't even backwards compatible with older versions of Outlook web mail, and by older I mean pretty recent versions... I had to resort to Opera to be able to access the web mail at work from home.

      Not that I use IE for anything else so I can't tell...

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    2. Re:So are they going to fix the issues wtih IE ? by Anonymous Coward · · Score: 0

      IE 10 and IE 11 are significantly buggy and seem to have broken compatibility with older sites whereas FireFox and Chrome still work on those sites perfectly well.

      Of course Microsoft would say fix the site but when you are dealing with sites that provide services to your business stability is king, as a result we have managed to stop IE10/11 being deployed on any of the Win 7/Win XP machines in use.

      Microsoft dropping support for older browsers means we will stop using IE, we had already started installing Chrome for compatibility reasons, looks like its going to be chrome all the way. If Google and Mozilla can maintain a decent level of backwards compatibility why cannot Microsoft.

      Ties in with the decision to stick on Win 7 because Win 8/8.1 breaks some of our applications, there is no upgrade option on those applications, they were written eight years ago and they HAVE to keep working.

      Microsoft needs to realise the business community wants stability, they don't want shiny new UI's and whistles and bells.

      If this was a face to face discussion I would be willing to bet you a nice bottle of something you like to drink that most of the sites that have issues with IE11 and not with FF and Chrome have issues because they browser sniff IE and send old IE code. With IE11 Microsoft has done what we asked all the time, to leave behind IE quirks and be more standards compatible. Serve it the same code as FF and Chrome, not your old IE code. As a web developer I'm as critical of old IE antics as anyone, but this is a good thing.

    3. Re:So are they going to fix the issues wtih IE ? by cyber-vandal · · Score: 1

      IE11 breaks loads of third-party apps and doesn't play nicely with some of Microsoft's own software like older versions of Sharepoint and Dynamics. I'm always tripping over IE11 issues at work and having to use Chrome instead because somehow the other browser makers seem to be able to not royally screw things up every time there's an upgrade. I'm not looking forward to IE12. At least the developer tools finally allow you to choose which Javascript file you want to look at rather than having to move through all the entries of a very unfriendly drop-down.

    4. Re:So are they going to fix the issues wtih IE ? by Anonymous Coward · · Score: 0

      With IE11 Microsoft has done what we asked all the time, to leave behind IE quirks and be more standards compatible.

      I seem to recall MS/Others making very similar if not the same claims about IE 7, then IE 8, oh and again with IE 9, oh yeah we 'finally' did it in IE 10, And now IE 11 and will probably promise 100% compliance with IE 12, then 13, 14, etc.....

      Yeah I' "Believe" it this time, riiiight...

    5. Re:So are they going to fix the issues wtih IE ? by Anonymous Coward · · Score: 0

      With IE11 Microsoft has done what we asked all the time, to leave behind IE quirks and be more standards compatible.

      I seem to recall MS/Others making very similar if not the same claims about IE 7, then IE 8, oh and again with IE 9, oh yeah we 'finally' did it in IE 10, And now IE 11 and will probably promise 100% compliance with IE 12, then 13, 14, etc.....

      Yeah I' "Believe" it this time, riiiight...

      If you are a web developer you don't have to "believe" anything, you can extremely easily verify yourself. Myself I've never heard Microsoft claim that you can server their browser same code as FF and Chrome before IE11.

  15. How is this going to play with ASP NET by Anonymous Coward · · Score: 0

    Quite recent versions of IIS running .NET4 ASP NET don't recognise IE11 and mess up the controls when they sniff the browser. You have to change the User-Agent string for them to work properly.

    This is MS shooting themselves in the foot. ASP NET should not do different things with different browsers period. Now unless some admin changes the IIS NET installation they won't work at all.

    1. Re:How is this going to play with ASP NET by bumba2014 · · Score: 1

      I stopped using ASP.NET Forms after the firsttime I used it on a project, I said never again, that has been many years ago. I suggest you do the same...

    2. Re:How is this going to play with ASP NET by Mondor · · Score: 2

      Sorry, I had no problems with ASP.NET (both WebForms and MVC) and MSIE 11. Could it be something in your code?

  16. Makes you wonder by Anonymous Coward · · Score: 0

    how MS ever got along before axing the dead wood. How did Steve Ballmer get the $ to offer to buy a NBA team before-the-axin-time? To whom was MS beholden then? Lean and mean? Or just mean?

  17. Yet, better than... by Anonymous Coward · · Score: 0

    ...Firefox's recent desire to break the UI regularly with "improvements" that I don't want. IE is worth looking at (esp. since I just spent a few hours thinking I had a bug in my code, but it turned out IE, Chrome, Opera, et al handled it fine - FF didn't). At least MS is providing support for something other than the latest version from yesterday which included major UI changes. This is where FOSS fails in comparison to a company that is paid to support its users and understands that people want to get their task done and are relatively uninterested in worrying about if they are using yesterday's software or last week's software.

    1. Re:Yet, better than... by Anonymous Coward · · Score: 0

      At least MS is providing support for something other than the latest version from yesterday which included major UI changes. This is where FOSS fails in comparison

      Yes, someone should tell Mozilla that having an extended support release of Firefox "for use by organizations including schools, universities, businesses and others who need extended support for mass deployments", would be a great idea!

  18. Please also stop supporting newer versions. by Jesus_666 · · Score: 3, Insightful

    Seriously; I'd be happy if Microsoft stopped supporting newer versions of IE as well. It's not that IE is a terrible browser per se, it's that Microsoft's policy of only releasing new versions of IE for versions of Windows they still support means that many people out there are stuck using ancient IE versions. This means that web designers often still need to care for things like IE 8 on Windows XP (which, to make things even better, behaves unlike IE 8 on other Windows versions) because that's what some customers use to see if their shiny new website works.

    No, those customers aren't going to replace their still-working XP boxes with brand-new computers running Windows 8.1 Upgrade 1 Patch 1 Service Pack 1, especially not to get a browser update. As long as those computers don't physically break down they're going to keep running Windows XP; after all, replacing a working tool is unneccessary cost and businesses don't like unneccessary costs. So IE 8 compatibility remains important, at least for those customers who still use it to look at their websites.

    All of that would change if Microsoft wrote IE to support the same platforms Firefox and Chrome do. Firefox 31 runs on XP SP2, as does Chrome 36. So should IE 11. Then we could finally move on from the days of horrible IE-specific hacks and dozens of kilobytes of compatibility code and actually get some work done. As it is, the only recourse we have is to keep telling people to never run IE under any circumstance except to download a better browser; hopefully at some point we will have drilled "IE is always the wrong choice" into people's head hard enough that they will reflexively use a browser with a sane update policy and IE will be marginalized enough to be irrelevant.

    Which would be sad; more competition in the browser market would be good. But not through an obsolescence factory like IE.

    --
    USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    1. Re:Please also stop supporting newer versions. by danielzip53 · · Score: 1

      Seriously?

      This is such an antiquated IT Industry philosophy! (if it ain't broke don't fix it).

      Thanks to this idea, Microsoft has to spend most of it's resources patching old systems, (which they no longer receive revenue for), making upgrading more expensive.
      Granted Microsoft needs to rethink how upgrades can be more efficient and provide a better model, but we could all benefit from a smoother and cheaper upgrade model especially if Microsoft didn't have to keep plugging today's security holes for yesterdays OS/Apps.

      How often do you (or the general populous) update you smartphone or tablet, just because there is a new version? or even install a beta/preview version? is it broken, does it need the update?

      Don't get me wrong I'm in Tech support, and I know the grind of change in both the App and OS development side is tough. But even for the apps I support, it makes me angry when someone requests a fix for an old version even though there's a new version. It takes time away from the development resource to fix a non-issue.

      Anyway rant over!

    2. Re:Please also stop supporting newer versions. by Jesus_666 · · Score: 1

      Well, to my knowledge this attitude is mostly found in non-IT companies. For them their computers are no different from, say, their plumbing. As long as the plumbing works (and there are no other pressing factors like legal requirements) there is no need to replace the pipes with new ones that may be in some way better. IT professionals understand that outdated software can (and often does) pose a security risk but most other people don't.

      Of course it would be nice if we could get people educated about that sort of thing. Then the only ones we'd have to worry about would be those who just plain can't upgrade - either because they have custom software or because their job-specific hardware has no drivers for modern Windows versions.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    3. Re:Please also stop supporting newer versions. by Bing+Tsher+E · · Score: 1

      They have really shiney file cabinets at the company that produces file cabinets. Their file clerks rate very high on the jobs satisfaction scores, too.

      It would be nice if we could get everybody else educated about the importance of file clerks and data custodians. And that nice gray crackle finish on the filing cabinets.

    4. Re:Please also stop supporting newer versions. by danielzip53 · · Score: 1

      Of course it would be nice if we could get people educated about that sort of thing. Then the only ones we'd have to worry about would be those who just plain can't upgrade - either because they have custom software or because their job-specific hardware has no drivers for modern Windows versions.

      So true, education is the key, move forward or don't complain about redundant old functionality with security holes everywhere. It gets to the point where silicon just won't fix your leaky pipe.

      Though;
      Custom software should always be being redeveloped etc, if it hasn't changed in a long time, then it's probably time to rethink it's purpose and efficiency. Plus specific to IE, IE "should be able to" handle all web comms since the dawn of time. (maybe if Microsoft had more resources this might be better)
      Backwards compatibility for hardware this is a tough one. Maybe it can only be solved by Microsoft providing some type of redundant API's for the ancient gear (maybe as like a non-standard package update).
      Basically like a hardware "sandbox" for the gear. Keeping the bloatware off the core OS.

    5. Re:Please also stop supporting newer versions. by drinkypoo · · Score: 1

      All of that would change if Microsoft wrote IE to support the same platforms Firefox and Chrome do.

      IE's only advantage is being closely coupled to the OS. Remove that advantage and there is absolutely no benefit to it. And Microsoft wants you to be locked in, they don't care if it's good for you.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Please also stop supporting newer versions. by cyber-vandal · · Score: 1

      Upgrading software isn't free, especially something like IE where each successive version breaks stuff that worked in the previous one.

    7. Re:Please also stop supporting newer versions. by Khyber · · Score: 1

      "This is such an antiquated IT Industry philosophy! (if it ain't broke don't fix it)."

      Yea, you go fuck your BIOS up just because you wanted some extra SSD speed. Watch your system brick out.

      Have fun with that BIOS hot swap, assuming that doesn't fail as well.

      There's a reason we don't fix non-broken things in the IT industry. It's called 'uptime.'

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    8. Re:Please also stop supporting newer versions. by smooth+wombat · · Score: 1

      Thanks to this idea, Microsoft has to spend most of it's resources patching old systems,

      If MS is spending most of its resources patching old systems, they're doing something wrong. Most of their resources should be spent on trying to develop new products.

      I don't hear car manufacturers whining they have to have parts available for 20 year old cars, and cars cost significantly more than any piece of software (excluding the crap from Oracle and SAP).

      And for the record, I do support as well as minor projects (hardware and software) so I'm well aware of what it takes to support products. Considering the amount of time I spend fixing the problems people have with the "latest and greatest", maybe companies should be spending most of their resources on patching and maintaining because they sure aren't getting the shiny new stuff right.

      Going back to the car analogy, if car companies said they would no longer support your vehicle AND not allow anyone to provide support, that you MUST buy a new vehicle every 1o years, I can guarantee you wouldn't have the same opinion.

      --
      We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
    9. Re:Please also stop supporting newer versions. by david_thornley · · Score: 1

      Get out of the IT business and top management would rather not think about IT any more than they have to. Any time or energy spent on managing IT is time or energy not spent on something that might increase revenue or seriously cut costs. IT is one of those support functions that isn't really related to what the business is about, like HR. Trying to convince them that they should update without need is not going to work, nor should it. (Trying to convince them that IT is a special snowflake isn't going to work either.) As it happens, more and more businesses are partly in the IT business, using computers and networking strategically, but there's still a lot of just plain infrastructure here.

      If there's a good reason to upgrade (security, for example), the head of IT needs to come up with a business case for updating, which includes discussing risks, how likely they are, and how much damage they could cause.

      There is custom software that just works fine, and doesn't need further development. Spending money on further development is a business expense and has to be justified on the basis of benefits and costs (which may include security concerns). There's a lot of processes in a business that are likely to stay the same for a long time, and so there's no need to keep changing the software. Also, although the software won't be perfect, the business can order employees to use it and deal with it, and this may well be cheaper than continued development. Finally, the source code may be gone. This is one of the things that shouldn't happen, but it does from time to time, and there's no point in disbanding the business and giving the money back to the stockholders just because some useful utility is without source code.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    10. Re:Please also stop supporting newer versions. by cbhacking · · Score: 1

      I actually like some of IE's features that other browsers don't have. Their tab grouping beats anything available out-of-the-box in Firefox or Chrome, and their Quick Tabs feature was excellent (until they inexplicably axed it in IE11). The built-in support for mapping or translating highlighted text is also quite nice. The best, though, is probably the built-in "tracking protection" (which actually makes an excellent ad blocker). I know there are other (niche) browsers with built-in ad blocking, but IE's feature automatically detects content (like tracking pixels and scripts) that is loaded from multiple addresses and blocks it. You can control the block lists (to, say, allow JQuery) and can also subscribe to third-party lists (EasyList, who are best known for their AdBlock Plus list, also have one for IE).

      Of course, once you add extensions, Firefox has a lot more features... but Firefox also still runs almost everything in a single process at Medium Integrity (normal user level) while Chrome and IE have per-tab processes and sandboxes.

      --
      There's no place I could be, since I've found Serenity...
  19. Don't forget #11 by bumba2014 · · Score: 1

    I suggest they stop supported version 11 also, that way a lot of problems in the internet will be solved.... Making a website will become much easier, less frustration and we could get payed a little better at the hour, not having to stay awake for nights getting it working on some version of MSIE...

  20. IE 9 will still be around for some time after that by Anonymous Coward · · Score: 0

    Vista, and hence IE 9, will be in Extended Support until April 11, 2017. Although it doesn't have near the same market penetration as XP.

    Also, can we assume by their explicitly listing IE 11 as the supported browser for most platforms after that date, that IE 12 won't be coming before 2016?

  21. As I said yesterday. . . by smooth+wombat · · Score: 1

    in the discussion about Skype being made to stop working with older versions of OS X and comparing it, Skype, to phone usage, when you can get Microsoft or Apple to have its software work for thirty or forty years like one can with a telephone, you let me know.

    Microsoft can stop support all it wants but that doesn't mean people aren't gong to stop using these older versions. People, particularly corporations, will tell them they're sick of constantly being forced to "upgrade" when there is nothing wrong physically or security wise with the browser they have, and have every new iteration be worse than the last as far as functionality is concerned.

    If you can't make security updates for a product which is more simple than the current version, you shouldn't be in the business of making software.

    --
    We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
  22. Wait for it... by Anonymous Coward · · Score: 0

    There will be an post along the lines of "IE exploits triple" when this happens.

  23. And I am reading this in IE 8 by jfdavis668 · · Score: 1

    We are so far behind. Still using IE 8 because our systems were developed for even older versions of the browser.

  24. Mail on a machine where you lack root by tepples · · Score: 2

    Webmail means not having to install software if you're borrowing someone else's computer to access your mail. Webmail means being able to access mail on a machine to which a proper MUA hasn't been petted, such as a video game console or something similarly locked down that happens to have a web browser.

  25. MSIE11 can't into Windows Server 2012 by Mondor · · Score: 1

    Ok, but MSIE 11 can't be installed on Windows Server 2012, only on Windows Server 2012 R2. Unlike the Windows 8.1, the R2 wasn't the free upgrade. So, if MSIE 10 won't be supported, can we still say that Microsoft is supporting the Windows Server 2012?

    1. Re:MSIE11 can't into Windows Server 2012 by operagost · · Score: 1

      The article, and the summary, say the "most recent supported version". This doesn't mean the latest version of IE for every supported platform will be the same version of IE. There's a chart right on the page. It's quite clear.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    2. Re:MSIE11 can't into Windows Server 2012 by Zaiff+Urgulbunger · · Score: 1

      You'd have to imagine that the reason for MS dropping support for older IE versions is to save on bug fixes for IE, and compatibility fixes for HTTP based products.

      So it would probably make better sense for them to work to enable newer IE versions on older OS versions. That said, what's logical, and what MS actually do often ain't the same!

  26. IE11=IE6 all over again by Maxwell · · Score: 2

    Sure, all we have to do is rewrite the internet to work with IE11 and we'll be fine. I propose Microsoft should start with Sharepoint, Project server, CRM Dynamics etc that currently don't work well with IE11...

    Firefox 3.6 has better overall compatibility than IE11!

    1. Re:IE11=IE6 all over again by Anonymous Coward · · Score: 0

      >Firefox 3.6
      what are you smoking? FF3.6 never went past 95/100 on ACID3. IE11 is currently 100/100 on ACID3.

      but don't let facts get in the way of M$ bashing

    2. Re:IE11=IE6 all over again by Anonymous Coward · · Score: 0

      I wasn't aware that a test coded to test the corner cases of JS (and to some extent, CSS) specifications was the sole metric of compatibility for web browsers.

      (By the way, to the best of my knowledge, no browser has passed the ACID3 test yet. Has anyone even read the 'the animation has to be smooth' rule?)

  27. Even Microsoft's websites doesn't support IE 11 by chiefcrash · · Score: 1

    Seriously, try enabling Microsoft Update with IE 11 installed...

    It just points you to a web page telling you to use Windows Update. If you need Office updates, you have to downgrade to IE 10, enable MS Update, and re-update to IE 11...

    --
    Show me on the 1st Amendment bobblehead where the moderator touched you...
  28. finally... an end is in sight. by netsavior · · Score: 1

    "Give me a modern responsive look and feel, it must be fast and single-page, and it should work on phones and ipads like the facebooks"... "Oh and half our customers use IE7 and have 512 megs of ram."

    I am counting the days until 2016!

  29. I would love to put auto update on by Stan92057 · · Score: 1

    I would love to put auto update on but, Microsoft among many other corporations' breaking the trust of people by sneaking in programs that are not updates. Sucks but ya reap what ya sow. I trust no Corporation, not even the FOSS ones .And that is IMO based on past actions

    --
    Jack of all trades,master of none
  30. hum by Anonymous Coward · · Score: 0

    Windows 7 IE 11 sucks balls when it comes to playing flash, html5, silverlight videos which are all choppy and not as smooth as chrome or fireflox. But! Firefox and IE 11 are both the same when it comes to choppy and slow time displaying web pages when flash plugin is enabled, disabling flash fixes the problem. Even with IE 11 video acceleration disabled it's still same issue unless it does not run well with amd phenom ii x6 processors. But I don't remember having this issue under windows 8/8.1 and I'm gonna test this out with the windows 8.1 enterprise 64 bit evaluation.

    But when it comes to security there is plenty of customization for it in IE to make it hard as a rock.

  31. KB2670838 by blivit42 · · Score: 1

    I can't use IE10 or IE11 due to the forced KB2670838 update that comes with them. For me, KB2670838 breaks the Resource Monitor in Windows 7 that you can launch after bringing up the Task Manager with ctl-alt-del. I use this quite a bit to monitor memory usage of processes, disk accesses, etc. This has been a known problem for quite some time, ever since IE10 came out. Just google for "KB2670838 resource monitor". If you uninstall KB2670838 in order to get Resource Monitor to work again, it uninstalls IE10 and IE11, since evidently they depend on it for whatever reason (I am not aware of any other software that requires this update to function). I normally wouldn't be too upset over them dropping support for legacy browser versions, but if they can't get off their butts to either fix KB2670838 to not break Resource Monitor, or fix Resource Monitor to not be broken by KB2670838, then I'm going to have to give them crap over this decision. I'll start using IE11 once it stops breaking Resource Monitor.

    1. Re:KB2670838 by Anonymous Coward · · Score: 0

      If you uninstall KB2670838 in order to get Resource Monitor to work again, it uninstalls IE10 and IE11, since evidently they depend on it for whatever reason (I am not aware of any other software that requires this update to function).

      clearly they want to discourage you from using resource monitor to spy on IE10 and IE11

  32. breaks lifecycle expectations by Anonymous Coward · · Score: 0

    that essentially what ships ON THE DISK is supported for the duration of support lifespan for the operating system (or office edition), as has been the case since the beginning of time for microsoft products...

    examples: its why ie6 lasted through xp's own lifecycle and why fpse hung around at least until the eol of office 2003... and also why some previously bundled features of windows were pulled out of windows itself, so they wouldn't have to be supported that long (photo gallery, mail, etc, now bundled separately).

  33. Welcome to the new browser wars by Anonymous Coward · · Score: 0

    Competition's never a bad thing. I'll take three viable web browsers over two. No-one wants to go back to the days of sites targeting specific browsers. "Best experienced with Netscape" - screw that.

    Mobile version... with separate hacks for android and iPhones! Yay! Native apps! Double yay! Welcome to the 1980s!

    Let's face it, web devs are insane. If they weren't, they'd code to standards and tell their bosses "I dunno why it doesn't work with your 10 year old phone (or brand new phone) but the problem is in your device not the server. You shouldn't have bought that phone, I recommend you return it."

    But there's always some idiot who says "oh, I can hack around that problem" and there you go, standards down the toilet again. They're insane.

  34. 41```4443331444`3142223`443``4`4`4`44 by Anonymous Coward · · Score: 0

    42111`44444``333324444444`3144`44444444444``4`4434`443344444444444444`414`44444444`244444244444444`44$444444444444444444`444444444443444`444444444$`4`44444444444444444134`4144444444`4444`4$44444444443

  35. Typical low-life of the field talking in you by Anonymous Coward · · Score: 0

    Menial little sysadmin (user of programs that truly skilled people write for you in developers and all YOU are, is a mere user, an end-user only, just with a better password, nothing more) complaining about developers (without which YOU would be helpless, you little pitiful stooge), who do what losers like YOU never could, period. You and your kind make me, laugh. You complain endlessly, but can't do the job without those you complain about.