Slashdot Mirror


The Man At Microsoft Charged With Destroying IE6

Barence writes "The man in charge of Internet Explorer has told PC Pro that he's been tasked with destroying IE6. Internet Explorer 6 continues to be the most used browser version in the world at the ripe old age of nine. IE6's position as the default browser in Windows XP means many companies still cling to the browser. 'Part of my job is to get IE6 share down to zero as soon as possible,' said Ryan Gavin, head of the Internet Explorer business group. Microsoft has also been giving further previews of Internet Explorer 9, with demonstrations showing two 720p HD videos running simultaneously on a netbook, thanks to IE9's GPU-accelerated graphics."

43 of 458 comments (clear)

  1. EOL XP already... by LostCluster · · Score: 3, Insightful

    To kill IE6, kill XP. Here's how.

    1. End all security updates for XP.
    2. Wait for the first botnet to come up with a XP hack.
    3. Say "Sorry, you need to upgrade. Now!" to the crying victims.

    1. Re:EOL XP already... by spazdor · · Score: 4, Insightful

      you forgot: 0. Design an OS which can viably replace XP. No, Vista doesn't count. 7 is getting there. Maybe.

      --
      DRM: Terminator crops for your mind!
    2. Re:EOL XP already... by Anonymous Coward · · Score: 5, Insightful

      7 is well beyond a viable replacement for XP in any useful category you can pick. The time to upgrade is here.

    3. Re:EOL XP already... by h4rr4r · · Score: 2, Insightful

      4. Watch businesses go else where

      Enterprises just got to XP a few years ago, it will be another 2-5 years before most of them are over to Win 7.

    4. Re:EOL XP already... by h4rr4r · · Score: 2, Insightful

      There is a ton of enterprise software that is not approved to be run on anything newer than XP SP2. This is pretty normal lag for this sort of expensive garbage.

    5. Re:EOL XP already... by spazdor · · Score: 2, Insightful

      You might get better performance in the VM if you give it 2 virtual CPUs. Depending on the specifics of your hardware, even if you use CPU affinity settings to force it to only execute on one CPU, you may find that concurrent processes get handled a little more gracefully.

      Sorta like 'hyperthreading', but implemented in software.

      --
      DRM: Terminator crops for your mind!
    6. Re:EOL XP already... by Gadget_Guy · · Score: 2, Insightful

      -1 Flogging a dead horse! Everyone kept attacking Vista with the vague DRM claims without being able to back it up. That was what made me the most mad when I eventually and begrudgingly tried Vista only to find that most of the complaints that I read about it were crap. I found that I could rip CDs in MP3 format with Windows Media Player, I could rip DVDs and I could play pirated videos downloaded from the Internet (presumably - not that I actually did that!)

      When you look at the specific claims people made about DRM, half the time it was just made up and the other half tended to be changes in the driver models (which lead to some hastily made and incomplete drivers).

    7. Re:EOL XP already... by webheaded · · Score: 2, Insightful

      Unfortunately, if you go into the future kicking and screaming you will indeed find some "features" are missing. It sucks, but sometimes you just need to sit down and adapt. Hell, you may eventually come to like it. Yes, I will fully agree there is some really irritating shit in Windows Vista/7. Notably the network center...GOD I hate that. However, I imagine it will eventually bother me less as I get used to it.

      Really though, the point I'm trying to make is that all the things you are bitching about are inconsequential and that the OS is honestly quite good. And this is coming from a person that was using Linux more than Windows at one point. I actually LIKE Windows 7. It's pretty nice.

      --
      "Those who would sacrifice essential liberties for a little temporary safety deserve neither liberty nor safety." - BenF
    8. Re:EOL XP already... by Just+Some+Guy · · Score: 2, Insightful

      Windows XP works nicely on a 1GHz Mobile P3 CPU and 512MB of PC133 RAM. Since 7 is a good replacement for XP, it will surely work just as fast as XP works now. Right?

      It's odd. On one hand, you like your dad well enough to maintain his computer for him. On the other, you won't give him anything newer than 9 years old. My suggestion: go to Target, pick up an HP Mini with twice the CPU and RAM, a hard drive about 15 times bigger, and vastly better graphics. For $300, you can go back to passive-aggressively neglecting him for another decade.

      --
      Dewey, what part of this looks like authorities should be involved?
  2. Support IEX9 on XP by figleaf · · Score: 5, Insightful

    If IE9 is supposed to destroy the previous versions of IE then they better support IE9 on XP.
    XP is still a solid operating system and currently has the highest market share.

    No one is going to upgrade their OS just because there is a new browser from Microsoft.

    1. Re:Support IEX9 on XP by AdmiralXyz · · Score: 2, Insightful

      Will people please stop with this stupidity? Microsoft isn't releasing IE9 for XP, not out of some evil plan to force you to upgrade, but because XP just doesn't have the technology: IE9 uses the Direct2D and DirectWrite APIs for its hardware acceleration, and these APIs didn't exist until Windows Vista. Writing security patches for an old operating system is one thing, but it's totally unreasonable to expect Microsoft to completely rewrite the graphics layer of a decade-old, non-current OS that will be EOL'd in two years' time.

      --
      Dislike the Electoral College? Lobby your state to join the National Popular Vote Interstate Compact.
    2. Re:Support IEX9 on XP by TheRaven64 · · Score: 4, Insightful

      Also, make it possible to keep IE6 installed for the Intranet. I suspect that most current IE6 deployments are corporate networks where IE is required for the Intranet, and therefore used everywhere. Make IE8 able to install along side IE6, but designate some domains or IP ranges for use by IE6. When you click on a link, it opens in IE8 by default, but if it's on one of the IP ranges designated as your corporate Intranet (configurable when you prepare it for installation) then it loads with IE6. Or just uses the old rendering engine. For bonus points, uses the old rendering engine in a sandbox where it can't escape even if it's completely compromised.

      The goal isn't to get rid of IE6, it's to get rid of IE6 from the Internet. If you can keep it around for the Intranet, but prevent it from being allowed to access any sites other than the ones designated as needing it, then that would be fine. Until, of course, those sites can be fixed, but the middle of a recession isn't the best time to ask companies to upgrade core infrastructure that still works.

      --
      I am TheRaven on Soylent News
    3. Re:Support IEX9 on XP by Anonymous Coward · · Score: 5, Insightful

      Firefox 4.0 will support Direct2D and DirectWrite API when available.
      Firefox 4.0 will work on XP.

      The real problem is there 'lack of will' on Microsoft's part and not a 'technical reason' as they would like us to believe.

    4. Re:Support IEX9 on XP by zuperduperman · · Score: 3, Insightful

      It's not stupidity. Somehow every other browser maker manages to get by on XP and do so with good performance, yet it's too much for Microsoft the MAKER of the OS itself to figure it out? Believing that story is "stupidity".

      If XP doesn't support the acceleration then you just write an emulation layer for that part and tell people that the XP version of IE9 is slower and they should upgrade windows to get some awesome speed boosts.

      Whichever way you spin it Microsoft is doing this by *choice*. They *chose* to use APIs not available to XP in the first place. Then they *chose* not to bother back-porting an emulation layer for the XP version to use. These choices are devastating to we developers who now confront the reality that the so-called "HTML5" revolution is, in reality, going to take 3 - 4 years more to arrive - holding back the entire internet because one single company couldn't bothered to spend a few developer hours.

    5. Re:Support IEX9 on XP by diegocg · · Score: 3, Insightful

      They could do this if Windows wasn't a crappy product that has a browser tightly with the OS. Firefox (and many other sane software) can have multiple versions installed and used at the same time (the Firefox Portable Edition for example). But due to the way IE is "designed", somehow it needs to be "integrated" to work properly. That's why trying a IE beta is such pain, you are forced to get rid of your stable version and keep a unstable version that can break multiple things.

    6. Re:Support IEX9 on XP by thegarbz · · Score: 4, Insightful

      "Hey Boss Boss, I got a crazy idea. XP is our most widely deployed operating system"
      "But it'll be EOL in 2 years"
      "Yeah beside the point, but how about we release a service pack completely re-writing the graphics APIs"
      "..."
      "That way people can run IE9 on windows XP. You see people won't need to upgrade to our new OSes"
      "..."
      "Everyone content with a 9 year old operating system can keep using it if we add new technologies. It saves them buying a completely new OS."
      "..."
      "Yeah sure ok we may be breaking some older systems with a service pack that completely screws with the graphics layer, and yeah it'll cost a few thousand manhours to write the code, but think how happy our clients will be when we remove all incentive for them to upgrade by backporting our great new features into the old dog."
      "..."
      "..."
      "Get out. NOW!"
      "yessir"

    7. Re:Support IEX9 on XP by value_added · · Score: 4, Insightful

      a decade-old, non-current OS

      Your points are generally valid, but let's skip the exaggerations. I'll quote from Wikipedia to make things easy:

      Windows XP was first released on October 25, 2001, and over 400 million copies were in use in January 2006. It was succeeded by Windows Vista, which was released to volume license customers on November 8, 2006, and worldwide to the general public on January 30, 2007. Direct OEM and retail sales of Windows XP ceased on June 30, 2008.

      So according to the above, Windows XP is, at most, 3 years past the time it was last sold retail. To use a car analogy, if you bought a new car off the showroom floor a few months after at the end of the model year, did you buy a used car?

      But even that is overly-simplified. The real world is always more nuanced and complex that, particularly with respect to enterprise customers. For that, you can consult the microsoft site, or talk to your sales rep.

      So no, XP is not a decade old. More importantly, XP (and IE6) is very much in use and relied on.

    8. Re:Support IEX9 on XP by MobyDisk · · Score: 5, Insightful

      NNNnnoooooo!!!!!!!!! ...death..gurgle...

      I work at a company that operates exactly as you specify. Some intranet software requires IE6. And sometimes particular versions of it too. Then some department installs an app that requires IE7 and the intranet app breaks. In one case, a manager suggested everyone install a virtual machine to run the apps that require IE6. That's just ridiculous.

      For some reason, corporate intranet software is always the worst-designed garbage. Killing IE6 will force these imbeciles to stop writing these garbage ASP+VB6 ActiveX apps.

      middle of a recession isn't the best time to ask companies to upgrade core infrastructure that still works.

      But the infrastructure doesn't work. Companies keep paying more IT staff to come-up with complex workarounds rather than fixing miniscule bugs. This will force the issue. It is happening anyway - soon we won't be able to get XP machines anymore. Already we have to pay to downgrade from Windows 7. Soon the hardware won't support Windows XP drivers.

    9. Re:Support IEX9 on XP by MightyMartian · · Score: 4, Insightful

      The other browser makers have a vested interest in as wide a level of compatibility and interoperability as possible. Microsoft's vested interest is the exact opposite. Microsoft needs to have the killer app that will drive everyone towards the latest version of its operating system.

      Of course, unlike even a few years ago, the growing success of third party browsers means that the chief piece of software that could drive users hanging back into upgrading is being removed, while at the same time that newfound competition in the browser market means Microsoft is less able to use the old tactic that worked so well with IE6 in deliberate non-compliance and incompatibility, because to do so would in fact now likely cost it even more market share in the browser world.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    10. Re:Support IEX9 on XP by Luckyo · · Score: 2, Insightful

      I find it quite hilarious how many people have already forgotten the main reason why all those APIs, or specifically the API package called "directx10" was never released for XP.
      It was to sell the unholy abomination that was vista.
      But it sure is fun to pretend that XP is some sort of uber-old tech and microsoft didn't implement dx10 for it because it's so old. I mean all those user-made mods to make dx10 work on XP clearly don't exist!

      XP is perfectly fine. It's a great OS, with significantly lower system requirements. Heck, outside the inane "but w7 works on my shitty, prehistoric laptop just as well as XP! HONEST!" claims, even game publishers with their infamous dishonesty when it comes to minimum system requirements have grasped that they have to essentially print "will need one extra gigabyte of RAM to run the game if you're using w7 instead of xp" on their game boxes.
      Check yourself if if you don't believe me. Pretty much every single modern game says "minimum requirements: x GB ram for xp, x+1 GB of ram for vista/w7". Because games actually need a somewhat responsive system to be playable, rather then one that is swapping like mad all the time because the operating system needs the extra ram.

    11. Re:Support IEX9 on XP by cowboy76Spain · · Score: 2, Insightful

      For some reason, corporate intranet software is always the worst-designed garbage.

      Because they can asume that they are working in a monoculture where they can be sure which versions of OS, browser and plugins will be already installed. This makes following standards less important in relation to other aspects (speed of development, features, etc.).

      But the infrastructure doesn't work. Companies keep paying more IT staff to come-up with complex workarounds rather than fixing miniscule bugs

      I think you are underestimating the costs of the fixes. It is not only the cost of the fix, but also the cost of reworking the systems that already relied or worked around those bugs (and the cost of detecting and working around possible new bugs).

      I mean, we have a number of "bugs" in our systems (v.g. a HR DB in MS Access 97 where we have to work around limits to the number of modules); in these kind of systems doing changes is effectively more complicated that it should be, but as we change only little parts of systems that are already working it still is better than rewritting it from scratch. Also, the former costs are "operation" costs while the latter are "inversion" costs, and it is way easier to get operation funds than inversion funds (it has always been this way, and with the crisis it has been reinforced). To get inversion funds, we have to promise a considerable reduction of operation costs.

      --
      Why can't /. have a rich-text editor? Editing your own HTML is so XXth century.
    12. Re:Support IEX9 on XP by Anonymous Coward · · Score: 1, Insightful

      "For some reason" is because decent programmers don't want to work somewhere that they aren't valued and have no hope of a promotion or decent raises, so non-software companies with internal IT staffs end up only being able to hire the worst programmers who can't get jobs elsewhere. These people then deliver as little as possible to a non-technical audience, where "look, it works" is sufficient with no further investigation into things like "it was written well and will continue to work in the future", and then they surf the web until 5:00 quitting time.

      Anon because my paycheck has depended on such environments before and may again in the future, although God I hope not.

    13. Re:Support IEX9 on XP by gad_zuki! · · Score: 2, Insightful

      XP has been a borderline mess since day one. We simply learned to work around its problems. Default admin user, no UAC, fisher price colors, a security nightmare that requires several types of anti-virus strategies, and lack of some basic features like native DVD burning or large file support for its zip handler. I avoid XP like the plague. Vista post SP1 is so much better of an OS its not even funny. Win7 vanilla is just as responsive on old hardware.

      Sorry, but this revisionist love-affair people have with XP is ridiculous. The sooner we get rid of it, the better for everyone.

  3. Let people run IE7 on Windows 2000 by Windcatcher · · Score: 3, Insightful

    If they really want IE6 usage to reach zero, the people at MS will have to swallow some pride and realize that there are some of us who refuse to 'upgrade" like little sheep. Otherwise, IE6 will still be around for quite some time. Oh, wait, Firefox 3.6 runs on Win2k...never mind...

  4. IE6 "Compatibility Mode?" by starseeker · · Score: 4, Insightful

    The problem, in the simplest terms, is that there are too many IE6 only sites and applications that are currently working "well enough", particularly internal to companies, and mucking with something that works already is a non-starter for many management types. No matter how much sense it makes to us, to them it's just money spent and risk taken to get back to where they currently are, functionality wise.

    Could IE introduce a sort of "browser virtual machine" where IE9 would start up what would internally amount to a sandboxed version of IE6 if it ran into an IE6 only site? (Of course, that begs the question of recognizing such a site, but presumably Microsoft would stand some chance of recognizing such behaviors since they created IE6 to begin with.) If you can't kill the old applications, you've got to work with them if you want to kill IE6 - perhaps IE9 could borrow a page from the VMWare/VirtualBox world and sort of do a "browser within a browser" to try and maintain compatibility while isolating the IE6 badness from any sane webpage? OSX provided a bridge for old Mac applications when they appeared on the scene which amounted to an old Mac within the new environment, so perhaps that's another possible model.

    Dunno if it's workable even in principle, but I don't see how else to move stubborn IE6 users.

    --
    "I object to doing things that computers can do." -- Olin Shivers, lispers.org
  5. With IE6 compatibility mode. by khasim · · Score: 2, Insightful

    IE6 will die ... eventually. When WinXP dies.

    But Microsoft pushed for too many IE6-specific extensions for their development products.

    Now companies NEED to run IE6 or spend time and money (and pain) re-writing the crappy apps that have evolved over the last 9 years.

    To replace IE6, you need to wait for WinXP to die or you need to offer IE6 compatibility in the new browser.

  6. First HTML 4, then HTML 5 by VGR · · Score: 3, Insightful

    I keep hearing about how IE9 will support HTML 5. I would much rather hear about how it will fully support HTML 4 and CSS 2. I'll even settle for its supporting 95% of HTML 4 and CSS 2.

    I keep hearing about how IE9 will support HTML 5 media elements like <video> and <audio>. I'd much rather hear about IE9 correctly rendering nested, cascading <object> elements as HTML 4 describes.

    Get the HTML 4 stuff working before trumpeting about HTML 5 functionality, please. God knows you've had enough time.

    --
    The Internet is full. Go away.
  7. Karma is a bitch... by tlambert · · Score: 5, Insightful

    Karma is a bitch...

    I expect they are now regretting that the barriers they put in place to prevent IE6 being displaced by Firefox, Opera, and other browsers is now effective at preventing IE6 from being displaced by another browser from themselves.

    -- Terry

  8. You must be new here by mollog · · Score: 1, Insightful

    starseeker wrote; "but presumably Microsoft would stand some chance of recognizing such behaviors since they created IE6 to begin with."

    Since when did Microsoft start caring about backward compatibility? Do you even know who we are discussing here? Microsoft has been rather craven about forcing users of its applications to upgrade. They don't make money by allowing people to stay with older operating systems and applications. And now that Apple has passed them in market capitalization, the heat is on to improve profitability. They don't know of any other way to make money than to force people to upgrade.

    --
    Best regards.
    1. Re:You must be new here by EvanED · · Score: 5, Insightful

      Since when did Microsoft start caring about backward compatibility?

      Wait, what? When did Microsoft stop caring about backwards compatibility? Backwards compatibility was, for many years, the greatest asset that Windows had, and IMO is the biggest reason that it became as widespread as it is. It's also the source of many of their biggest security problems.

      In fact, in the last few years (with the end of the 9x series kernel, the introduction of XP SP2, the introduction of UAC, and the removal of the 16-bit subsystems in the 64-bit versions of Windows), they have shown a willingness to break backwards compatibility that they had basically never shown a decade ago.

      Forcing upgrades is a different matter, and is more concerned with forwards compatibility, which doesn't really have any bearing on this discussion.

    2. Re:You must be new here by fatwilbur · · Score: 2, Insightful

      This is an all-round stupid comment. As another poster writes, most of MS's operating system issues are/were caused by their unrelenting need for backwards compatibility. This actually allowed IT departments to afford upgrades, as very little other software required same-time upgrades.

      As for the market cap point, if you had worked for most any organization and saw how embedded Microsoft's business products are, you'd laugh at the prospect that a company making the current coolest cellphone is worth more. For the price Apple's shares are demanding, you could buy a company with two and a half times Apple's market share in smartphones (RIM), the worlds largest computer maker (Dell), the world's largest computer chip maker (Intel), and still have tens of billions left over to buy half the tech companies on Wall Street. Overvalued by a mile... hype does that.

  9. Dumb Demo... by HockeyPuck · · Score: 4, Insightful

    demonstrations showing two 720p HD videos running simultaneously on a netbook, thanks to IE9's GPU-accelerated graphics

    How about demonstrating flawless backwards compatibility with ancient activeX plugins on Oracle financials running under winXP...

  10. m$ and browsers by Ice+Station+Zebra · · Score: 1, Insightful

    M$ spend YEARS ignoring browsers. "IE is good enough." Now that they have competition they care again about their browser. IE9 will be the bestest browser EVER! (What happened to IE8?) Will businesses finally see the light and realize that M$ is ONLY IN IT FOR THE MONEY. I hear the iPeople out there saying "Apple. Apple is better". No they are WORSE. Proprietary software and PROPRIETARY HARDWARE. Think IBM Mainframes baby.

    Destroy IE6. How about money back to all the copies of Vista you forced on people who had to buy a new computer? Don't thrust them, microsoft, they will stop caring as soon as the market share is back up to 99.999999999%. Mr. Charged with destroying IE6 will be out of a job. Ready the "This site best viewed in IE9" banners so called webmasters. The internet will suck once more.

    1. Re:m$ and browsers by RyuuzakiTetsuya · · Score: 4, Insightful

      Proprietary software and PROPRIETARY HARDWARE.

      I didn't think BSD and Webkit were proprietary software and I certainly didn't think that x86 was proprietary hardware either.

      Apple's been promoting a browser-agnostic web experience. They are better. They're contributing to open source. That does make them infinitely better.

      When MS ships something like WebKit, Darwin or Grand Central Dispatch, we'll talk about who's better than who in the software field.

      --
      Non impediti ratione cogitationus.
  11. How about not. by Anonymous Coward · · Score: 1, Insightful

    demonstrations showing two 720p HD videos running simultaneously on a netbook, thanks to IE9's GPU-accelerated graphics

    How about demonstrating flawless backwards compatibility with ancient activeX plugins on Oracle financials running under winXP...

    How about not. How about we let that crap die and then dance on its grave.

    If your company was foolish enough to build its infrastructure on proprietary vendor-specific crap, then you deserve to get bitten in the ass when those proprietary vendors change their minds. Perhaps in the future you'll think more carefully. If not, well, there's always the VM option.

  12. Easy! by Gerald · · Score: 4, Insightful

    1. Go to the head of the Office business group.
    2. Make sure they drop support for XP in the next version of Office.

    IE 6 won't die until XP dies. XP won't die until Office won't run on it.

  13. Going after the users is the wrong way. by geekoid · · Score: 4, Insightful

    GO after vendors that still require there users to us IE6 in the work place.
    Once it's not in the work place, it will leave the home.

    I would love to get rid of it at work, but vendors(I'm looking at YOU Oracle) still have apps that require it.
    There slated to get rid of it, but not for 2 more years.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  14. Re:IE6 is NOT the most popular web browser... by adona1 · · Score: 4, Insightful

    This is the key. My company also rolled out a new intranet and only supports IE6 (in fact, they've issued warnings around the company that Firefox isn't secure as it doesn't received 'regular security updates'. Oh, the fun).

    However, the person they roped in to build the intranet included a few comments in the source code, specifically "Internet Explorer 6 is fucking terrible" "I had to hack this code to even get it to work" and an entire subfolder named "IE6sux".

    So that's what MS has to deal with, corporations who figure if it ain't broke then there's no reason to fix it. Problem is, they don't actually realise what 'broke' is.

    --
    Between the falling angel and the rising ape
  15. What barriers? by ClosedSource · · Score: 2, Insightful

    Including IE in Windows and making it the default browser isn't a barrier to using another browser. If it were nobody would be using other browsers today.

    1. Re:What barriers? by Phroggy · · Score: 5, Insightful

      Including IE in Windows and making it the default browser isn't a barrier to using another browser. If it were nobody would be using other browsers today.

      You clearly don't remember this, but from IE4 to IE6, Microsoft tried as hard as they could to push web developers toward proprietary technologies that were only compatible with Internet Explorer. They went out of their way to make IE's rendering engine try to guess what developers might have meant when writing sloppy non-standard code, which resulted in web sites that were designed exclusively for IE not working in any other browser (and being an enormous pain in the ass to fix). Also, because IE's support for the standards that other browsers were trying to implement was so shoddy, web sites designed for other browsers wouldn't work correctly in IE (also an enormous pain in the ass to fix), so there was a huge disincentive for developers who used IE as their primary browser (because it was bundled with Windows) to even try to support anything else.

      With ~90% market share, Microsoft decided that IE6 was "good enough" and shut down development. But IE6 wasn't good enough, and somebody decided to take the Mozilla Suite, strip out all the non-browser stuff (the email client, the address book, the WYSIWYG HTML editor, the IRC client, etc. etc.) and try to make a stand-alone browser people actually wanted to use. And, after awhile, people started using it, and Microsoft was embarrassed.

      So, they tried to clean up a few things with the release of XP Service Pack 2, then began an active attempt to make a browser that doesn't completely suck ass. They're years behind, and they know it, but they're slowly attempting to catch up. They also know they're not the leader of the pack anymore, so they have to cooperate with other browser developers and play the game on their turf, which is a weird thing for Microsoft to be doing.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  16. Corporate users by PPH · · Score: 4, Insightful

    I remember back when Microsoft was begging people to use IE6 and write apps to its API. In spite of all of the advice not to go down that path, some IT people did just that. They staked their reputation on that move. And now Microsoft expects these people to go to the BOD and say, "Remember how I begged you to go with IE6 a few years ago? And even though it was going to cost us a bundle in training, tools and development costs, it was going to be worth it. Because Microsoft promised us it was. Well, now they say we've got to spend a bundle more to undo all the crap we did. I know. They lied to us once. But we can trust them this time. Really. They wouldn't do it again, would they?"

    The people responsible for tying their companies to IE6 have made it a few steps up the management ladder. If you thought they had some pull back when they made that fateful IE6 decision, what sort of power do you think they have now? Microsoft wants these people to make what could be a carer limiting (or ending) move. They'll have to admit that they bought the Microsoft sales pitch back then, cost the company a bundle of money, and now it looks like it was money down a rat hole. Gavin needs the trust and good will of these people if he ever expects them to buy the next Microsoft package. This doesn't look like a smart way of doing it.

    --
    Have gnu, will travel.
  17. Re:IE6 is NOT the most popular web browser... by Dorkmaster+Flek · · Score: 2, Insightful

    Google isn't the only one gagging...

    --
    I like to think of online DRM as something akin to a college -- you pay for lessons until you learn something.
  18. Re:IE6 is NOT the most popular web browser... by Hurricane78 · · Score: 2, Insightful

    The real problem is experts who don’t have the balls to stand up to the management, and tell them that they know better (after all, that is the reason the are paid, no?), and that if they hire experts to then not listen to them, they are idiots and will fuck up their company. So what is the reason again, to work for a boss who deliberately destroys the company? I would go straight to the big boss, and tell him that that idiot is fucking up his company, and list all the ways that he hurts him and costs him money.

    Or in short: Geeks, you are the experts, so get some fucking balls! (And start searching alternative jobs, since you should always have at least one or two other places where you can go.)

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.