Slashdot Mirror


No IE7 For 2k, Now In Extended Service

Yankovic writes "Looks like MS will not support IE7 on Windows 2000. 'It should be no surprise that we do not plan on releasing IE7 for Windows 2000... [S]ome of the security work in IE7 relies on operating system functionality in XPSP2 that is non-trivial to port back to Windows 2000.' While security fixes will still be available until 2010, I guess that means the only browsers with tabs for W2k will be Opera and Firefox." All the details about an MS product's fall into senility available at the lifecycle page.

19 of 469 comments (clear)

  1. One More Reason to Keep Win2K by geomon · · Score: 5, Insightful

    My choice is to upgrade from Win2K to WinXP for IE?

    Hah! I'll keep Win2K and Firefox, thanks.

    --
    "Rocky Rococo, at your cervix!"
    1. Re:One More Reason to Keep Win2K by Karl+Cocknozzle · · Score: 3, Insightful
      My choice is to upgrade from Win2K to WinXP for IE?

      Hah! I'll keep Win2K and Firefox, thanks.

      Yeah, I'll second that emotion... Although my primary machine is a PowerMac G5, my secondary runs Win2k for games, and stuff that "only happens on Windows" (which ain't too much anymore.)

      If I'm completely crazy, somebody slap me, but wasn't Microsoft convicted of anti-trust violations relating to their monopoly on the browser? Wasn't a serious issue of their case the "need" to integrate Internet Explorer with the OS? Now it is MORE integrated--to the point that they CAN'T possibly make a Windows 2000 version?

      If this isn't more blatant abuse of their monopoly on the desktop, what exactly would it take for DoJ to take action? (Besides a new president?) Would Gates have to go on tv wearing a cape and a "PHantom of the Opera" mask and say "Muhuhahahaha! Fools! My dominance of your desktop is complete!" before the saps at DoJ think something is wrotten in Redmond?
      --
      Who did what now?
    2. Re:One More Reason to Keep Win2K by Patoski · · Score: 5, Insightful

      The point is that 2k starts its EOL cycle in June and goes into extended support (security updates only). Why would they spend all this time back porting stuff from XPSP2 to an EOL product. Guess what, 98 isn't getting IE7 either, is that an anti-trust violation or simply because 98 is in EOL status?

      Maybe because ~60% of their corporate userbase is still Win2k? Or how about the fact that they haven't released an enhancement to Win2k in over two years? C'mon folks, Win2k is only 12 months older than XP. The question real question is why wouldn't MS give Win2k users some love considering that the browser wars are starting to heat up again?

      So let's sum up the past two years of "Mainline Support" from MS for Win2k users: no Service Pack 5, none of IE6 security enhancements in XP will make it to Win2k and no IE7 for Win2k users.

      MS is really giving Windows 2000 users the middle finger. MS is partly responsible for the security mess that is Windows 2000 and they should do *something* to help fix the situation. It isn't my fault as a user that MS hasn't released an operating sysytem for going on four years now. Why would I now pay for an OS that is over 3.5 years old?

      It is really starting to feel that, at least part of the reason MS is going on an on about security is just another ploy to try to get customers to upgrade to the next greatest version of their product more quickly.

      If this story is accurate, then this is a huge misstep by MS. MS is really opening the door for Firefox to further accelerate its adoption.

      --
      G. Washington on Government "it is force. Like fire, it is a dangerous servant and a fearful master."
    3. Re:One More Reason to Keep Win2K by bluk · · Score: 3, Insightful

      That's not exactly fair. I don't like MSFT any more than any other company, but you can't force companies to support products forever. There are several applications that only work on certain OSes (even Mac programs sometimes require 10.3 and some Unix software requires at least a certain KDE or Gnome version). Some require certain libraries/DLLs or something like Cocoa Bindings (and in the future CoreData) that just aren't available on earlier OSes.

      Personally, if you need to sacrifice compatibility, I would rather have it than hold back any possible forward progress. Several problems exist today solely because of design problems made years earlier.

    4. Re:One More Reason to Keep Win2K by IntlHarvester · · Score: 4, Insightful

      Agreed -- That gets the real issue. Not IE7, but the fact W2K is going into "extended support" 1-2 years before Longhorn ships. If anything, it should be the other way around -- companies should have at least a solid year to evaulate Longhorn before being moved off 2K.

      Most corporations running W2K were early adopters for Microsoft, companies who either moved quickly onto 2K or upgraded from NT4. WinXP was sold as a consumer upgrade that provided almost no additional features for the corp user, so they passed. Now they (we) are being punished for the fact that Longhorn is years behind schedule. W2K might be old, but it's users are very entrenched customers.

      Note, normally I wouldnt stand for people bitching about a 5-6 year old OS, but in this case Microsoft has not delievered an upgrade and should extend the support window until they do.

      --
      Business. Numbers. Money. People. Computer World.
    5. Re:One More Reason to Keep Win2K by Seumas · · Score: 3, Insightful

      I stuck with 2000 for the longest time and spat on XP. I don't care for 2000, but since I had to have a couple windows boxes around, I demanded that they be 2000. But after having to account for extended LBA (for drives larger than 127gb) and other issues, I decided to give XP Pro a try. You know what? I actually am pleased with it. I'll still take my Debian or Gentoo, thanks - but for Windows, XP ain't all that bad.

      Just change your settings to get rid of all the XP GUI crap and change back to classical everything on the interface and you can't even tell you're using XP - except that more things work with less trouble than on 2000. And the crashes have been no more frequent than they were on 2000.

    6. Re:One More Reason to Keep Win2K by cwensley · · Score: 4, Insightful

      Wait one minute.. WinXP *IS* the upgrade for 2k. Do you see OSX users getting new functionality for older versions? No. They must buy the _next version_ of the os to get new features. I expect this is the case for about 99.9% of the software out there.

  2. Terrible Sunday News by fembots · · Score: 5, Insightful

    Does that mean I'm stuck with Firefox, and cannot utilize Microsoft's intelligent autoupdate which automatically downloads security patches once every 3 days?

    This raises an interesting question - Why/How can Firefox, which runs happily on W2K and others, offer better security, while IE cannot do the same on an OS developed by MS itself?

    I'm sure Firefox will be laughed at if it said it could not develop a browser for Windows because some of the security work in Firefox relies on operating system functionality in Linux that is non-trivial to port to Windows.

    1. Re:Terrible Sunday News by Ride-My-Rocket · · Score: 5, Insightful

      Why/How can Firefox, which runs happily on W2K and others, offer better security, while IE cannot do the same on an OS developed by MS itself?

      According to Microsoft, IE is integrated into the operating system itself -- it is no longer a standalone application. Ostensibly they did this to allow greater desktop-to-Internet integration, but given the inherent insecurity of ActiveX, the tendency for the forces of evil to use it maliciously, and the inability of users to lock it down, it's not exactly a hot selling point these days.

      Firefox, on the other hand, stands to benefit immensely from all this. It offers a free, lightweight, standalone browser whose programming environment makes it easy for developers to extend its functionality without coopting its security (so far). It does this without any hooks into the operating system, and offers a variety of ways to combat malware, popups and generally obnoxious behavior (Flash movies, rampant advertising, etc).

      Microsoft might claim that they won't be releasing any further security patches or functional upgrades to Windows 2000 or IE6. But as of September 2004, ~49% of Windows users still use Windows 2000 or lower (98, 95, NT, etc). Trying to scare users into upgrading their OS, so they can take advantage of a marginally improved, questionably more secure Windows, doesn't seem to be working anymore. And I'm by no means a Linux zealot -- I'm an ASP/SQL programmer, have been using Windows since v3.1, and am a huge fan of Microsoft's development tools / languages.

      Besides landing my most recent job, discovering Firefox was the best tech-related thing that's come along in recent memory. It's inspired me to start learning more about client-side development again, after seeing what's possible with AJAX (Asynchronous Javascript And XML), standards-compliant CSS and XHTML. Once Dean Edwards' CSS-based IE7 stylesheet matures a bit more, developers will be able to instantly upgrade the set of standards-compliant available to IE 5/6 users. At that point, who will need IE 7? The days of developing wonderful new HTML and CSS tags that are only supported by one browser are in decline...... Firefox's market share has risen to just under 10% in the past year, while Microsoft's market share has dropped to under 90% for the first time since Netscape was still relevant. IE7 won't become ubiquitous for a long, long time, especially if Microsoft doesn't plan on making it available to users of its older operating systems. Why would developers of any web applications besides IE-only Intranets/Extranets create products that utilized features only available to a very small set of the installed user base?

      So whatever, Microsoft. Dig your own grave, if you insist upon doing so. I'll continue to use your server-side tools, provided something better and easier-to-use doesn't come along, but at this point, you've lost me as a client-side developer of IE. Not that you should care, of course..... but if you can lose a devoted developer like me, I have to wonder how many others you've push away. It appears it's not all about "Developers, Developers, Developers!", as Steve Ballmer & Co. would have us believe.

  3. bad move on Microsoft's part by kalpol · · Score: 5, Insightful

    Many people are sticking with Win2K because of the draconian licensing and validation process required with WinXP. They will begin to lose a significant portion of the browser market as people realize how easy it is to get Firefox and the benefits it offers over Explorer.

    --
    12:50 - press return.
  4. The M$ resopnse... by hubang · · Score: 4, Insightful

    "Besides, if we supported our products with our products, nobody would have reason to buy our new products."

    Dramatized for your enjoyment.

  5. The cost of Internet Explorer by yotto · · Score: 5, Insightful

    So, Internet Explorer is no longer free, to get a secure Microsoft Browser (Yeah, I'm making a few assumptions here, but let's just live in the hypothetical word for a moment) I have to buy a new version of the OS? Or I can get a secure version of Netscape (That they call Firefox these days) for free. I wonder what I'll choose.

  6. Well thats going to be a big boost for firefox by mpcooke3 · · Score: 4, Insightful

    Most normal users never upgrades their OS and a lot of geeks prefer 2k to XP.

    I suppose they have to release something new in Longhorn, they could make the window borders even bigger and more ugly and cripple the performance a bit more but with all the things they've dropped from longhorn they need some killer feature like copying firefox tabs to justify forcing another pointless upgrade on the corporate world.

  7. Re:I... can't tell by mindaktiviti · · Score: 4, Insightful

    It's a good thing. Why? Well, if it needs the use of the service pack, that only seems to indicate that the browser is more and more tied in with with the OS (if that's even possible).

    Like someone mentioned on slashdot before (paraphrased):

    "I'd rather browse the net with a browser, not an operating system."

  8. Re:Wait a minute... by gad_zuki! · · Score: 4, Insightful

    >And I still don't trust SP2 and all the crap it dumps on your box.

    "Crap" like pop-up blocking for IE6, a better wireless manager, NX support, firewall on by default, etc? It blows my mind that all these windows users hate the system they use and complain when they get a bunch of needed features. Of course, there are issues with the update, but thats true of any modern OS.

    If you're using windows XP you should have migrated to SP2 long ago if you cared about security and stability. Then again this is slashdot, enjoy your ill-informed karma whore points.

  9. Re:Sounds like by dbIII · · Score: 4, Insightful
    And yet USB for NT 4.0 exists
    Where can it be found?
  10. Re:Lazy FUDer by Anonymous Coward · · Score: 4, Insightful

    The IE rendering engine with most of the features people get all gushy about in the Mozilla/Firefox browsers.

    Funnily enough, one of the things most people love about Mozilla/Firefox is that they don't use the IE rendering engine - they use one that can cope with ancient 1990s technology like XHTML and transparent PNGs and CSS layout instead.

    And, not to rain on your parade, a glance at the MyIE page shows that the wonderful features you're expecting me to be impressed by are... tabbed browsing and mouse gestures. Sorry, but as far as I'm concerned those are basic minimal features required for a browser to qualify as usable. I couldn't find anything there about a MyIE equivalent of Greasemonkey. Or Flashblock. Or EditCSS.

    Seriously, you should give Firefox a try (or another try, as appropriate). It's got all the features people get gushy about in MyIE, and many more, and - as an added bonus - it doesn't use the IE rendering engine. :p

  11. Wrong type of "compatibility" by xswl0931 · · Score: 4, Insightful

    Microsoft has a history of being backwards compatible (even to supporting buggy behavior in newer releases), but you're really talking about forward compatible rather than backwards compatible. Apps written for Win2k will work on Longhorn/XP, but apps written for Longhorn/XP may not work on win2k. At what point is a company allowed to stop adding new features to old products? Newer versions of cars add satellite radio, GPS, and MP3 capability, but I don't see any car companies provided these features on older models.

  12. MS and legacy support by WebCowboy · · Score: 3, Insightful

    Microsoft has one of the best track records in the business for backwards compatibility. ...except they don't. My employer guarantees 100% compatibility with 20 years of future products as a condition of sale. We have fully supported software that communicates with hardware that was made in the 1970s. IBM has that sort of track record of long-time compatibility and support for its mainframes too. That kind of track record for Microsoft would mean being obliged to offer support for stuff like BASIC on the TRS80.

    That being said, MS DOES put a great deal of effort into backwards compatibility--to the point of including a DOS emulator in NT4/2K/XP (WoWExec) that is so seamless most people would never think that the aforementioned OSes are no more compatible with DOS than Linux is (it just happens to have really good emulation). There is a blog by a microsoftie called something like "the old new thing" that explains the lengths MS goes to to maintain compatibility with popular legacy apps.

    There are two problems with the efforts MS has put into legacy support: Firstly, it has done a lot to make their codebase cryptic, nearly unmanageable and sub-optimal. This is a problem the likes of IBM and my employer have to contend with as well, except that DOS and NT were not engineered with then intention of being the core of a product for decades. As a result, you get a massive blocks of code, .ini files and registry settings specific to legacy apps. You might never run the DOS version of Simcity from 12 years ago on your new system, but there is code in the current windows that was placed there specifically to make that one app run. All of that legacy support is quite a hodgepodge at times.

    The second problem with MS Legacy support is that it tends to be rather selective. In the past, when there was a very popular 3rd party app that sold a lot of copies of Windows (certain desktop publishing packages come to mind) legacy support was done without question. when MS Office sales are slumping...well it looks like time to add a few more features that 0.001% of users asked for and use them as an exuse to break file format compatibilities. The thing about IE7 beig "too advanced" for anything older than XPsp2 is another one of those cop-outs. A little company and a non-profit foundation managed to make more secure browsers with innovative features that runs on multiple platforms and MS can't use their billions to engineer something that works with multiple versions of a SINGLE PLATFORM? Bullshit. They are trying to accelerate the elimination of Win2k because it is limiting their revenue potential.

    I understand that legacy support is expensive and that MS is beter than a lot of SW companies like Red Hat (not that that is totally Red Hat's fault--they just don't have the resources). The difference is that Free software often continues to work on anything it'll compile on, and if you do have to upgrade you don't often have to pay through the nose for a highly disruptive upgrade. The IE7 compatibility issue is artificial--MS could EASILY make it run on win2K with its resources and say "there is no official support--use at your own risk". They just made design decisions to deliberately create critical dependencies on XPsp2. Even more than concerns about support costs, MS wants to boost stagnant OS sales.

    Problem is, that makes IE7 an expensive browser for someone like me, whose only MS OS is win2K. Firefox is free in all senses of the word, so IE7 makes for a pretty weak justification for an OS upgrade when Firefox is much more convenient to get and I don't need to re-install my OS.