Slashdot Mirror


Microsoft Exploits Firefox 4 Uproar, Beats IE Drum

CWmike writes "A Microsoft executive late Thursday used the furor over Mozilla's decision to curtail support for Firefox 4 to plead the case for Internet Explorer in the enterprise. 'I think I speak for everyone on the IE team when I say we'd like the opportunity to win back your business,' Ari Bixhorn, director of IE at Microsoft, said in a post on his personal blog. 'We've got a great solution for corporate customers with both IE8 and IE9, and believe we could help you address the challenges you're currently facing.' Bixhorn addressed his open letter to the manager of workplace and mobility in the office of IBM's CIO, John Walicki, who, along with others, had voiced their displeasure with Mozilla's decision to retire Firefox 4 from security support. In a comment appended to a blog maintained by Michael Kaply, a consultant who specializes in customizing Firefox, Walicki called Mozilla's decision to end security support for Firefox 4 a 'kick in the stomach.'"

26 of 315 comments (clear)

  1. Duh by Spad · · Score: 5, Informative

    Hardly surprising; businesses like some stability in their apps. You don't want stagnation, but you don't want to have to test and deploy entirely new releases every 3 months just to maintain a supported environment either.

    I'm not sure Microsoft need to be worried about that particular market anyway because, as much as I hate to say it, IE is really the only browser that's suitable for use in a large Windows environment. It has ludicrously granular control available via Group Policy and updates can be deployed via WSUS without needing any user interaction or elevated rights. Firefox doesn't even offer an MSI installer, let alone any practical way to manage settings or control updates across multiple machines (but then Chrome, Opera and Safari are similarly lacking so they're hardly alone in that regard).

    1. Re:Duh by Qzukk · · Score: 5, Informative

      Chrome, Opera and Safari are similarly lacking

      http://www.google.com/apps/intl/en/business/chromebrowser.html

      MSI installer with Group Policy support (in addition to the "Internet Properties" that Chrome already taps into for proxy configuration, etc)

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
  2. Re:You had me at... by Spad · · Score: 3, Insightful

    Why wouldn't they? I mean, IE isn't my cup of tea and standards support is still a little behind the curve (though improving) but IE8 and certainly IE9 are solid browsers for your average corporate user.

    I often get the impression that some people are rather stuck in the IE6/XP era when it comes to any product that Microsoft puts out; they're not *all* shit you know :)

  3. Driven by vendor lock-in by slashqwerty · · Score: 4, Insightful

    Microsoft gives IE away for free. The only reason they want to "win back your business" is to take advantage of vendor lock-in. I'm not seeing where this is good for the business, especially considering that the security fix for Firefox 4 is well-known and free (upgrade to Firefox 5).

    1. Re:Driven by vendor lock-in by Crazy+Taco · · Score: 3, Insightful

      I'm not seeing where this is good for the business, especially considering that the security fix for Firefox 4 is well-known and free (upgrade to Firefox 5).

      That's because you don't understand how a large corporation works, and have never worked for one. Large corporations have many THOUSANDS of custom written applications, as well as many 3rd party applications they buy that rely on a browser (typically IE). They need time to test all of these apps before upgrading the browser to make sure things don't break. For example, our company uses Remedy, a 3rd party client application, for IT change management/incident reporting. Unfortunately, though it is mostly a stand alone client app, Remedy uses the IE engine (via some IE.dlls) for display. An upgrade to IE 9 (at least on the version of Remedy we are on) instantly breaks it so that you can't read tickets. Similary, some SAP Netweaver components throw a "browser is not supported" message for IE 9. Some of our custom apps, especially the older ones written in early ASP .Net or Classic ASP, do not display correctly on the new version. Some 3rd party browser plugins don't work. Security testing needs to be done.

      All of this takes time. Everything has to be tested, and all the problems like those mentioned above have to be ferreted out and mitigated before the new browser can be rolled out, or key productivity tools and processes will break. That is why a stable release cycle, as well as security support for older versions (rather than instant End of Life) is critically important to businesses. It has nothing to do with "vendor lock-in" as you suppose.

      --
      Beware of bugs in the above code; I have only proved it correct, not tried it.
  4. Plugins needlessly broken by new version number by dreamt · · Score: 5, Insightful

    Part of the reason that I'm pissed off by this version a week crap is that plugins that should work no longer do, simply because they expect a version number. Google Toolbar doesn't work because of that. That's a serious WTF moment.

    1. Re:Plugins needlessly broken by new version number by The+MAZZTer · · Score: 4, Informative

      Many addons reach into the internals of Firefox... which can change frequently and without warning between versions. Mozilla will automatically update addons now to be marked compatible if it detects they don't make use of changed APIs I believe.

      Chrome has the exact opposite system: Extensions are tightly sandboxed and a limited API is exposed. As long as that API continues working the same way all extensions coded for any version will work. Of course extensions can't hook into the browser all the ways that Firefox ones can.

    2. Re:Plugins needlessly broken by new version number by wizardforce · · Score: 4, Insightful

      poorly programmed extensions are not Mozilla's fault. The attitude that emulating browsers like Chrome's development cycle is a good idea is Mozilla's fault. They're working on features like having the tabs way up top rather than fixing trivial things like Java plugin incompatibility (which works fine in chrome but crashes firefox) or dealing with the massive memory leak problem that firefox has had for years and has yet to actually try to fix. they need to get their priorities straight or they're going to die.

      --
      Sigs are too short to say anything truly profound so read the above post instead.
    3. Re:Plugins needlessly broken by new version number by BZ · · Score: 4, Informative

      If your addon is on addons.mozilla.org, then it got checked for compat with Firefox 5 and automatically version-bumped if it was compatible.

      If your addon is not on AMO, you don't need to worry about AMO's policies.

      Google Toolbar, for example, is not on AMO.

    4. Re:Plugins needlessly broken by new version number by wizardforce · · Score: 5, Informative
      --
      Sigs are too short to say anything truly profound so read the above post instead.
  5. Version numbers are meaningless by BagOBones · · Score: 4, Interesting

    Each company and such has a bizarre meaning to version numbers.
    FF 5 IS the security update to FF4.
    Much like Chrome goes up by major numbers.

    Then you look at open source where things often start in the 0.01 range and every digit could be a new feature release.

    A number of companies use major.minor.build however it really isn't as standard as you think.
    Cisco ASA devices look like major.minor.build however new features regularly appear in the "Builds"

    Juniper security gear has gone to a year.quarter. release numbering system

    take your pick.

    --
    EA David Gardner -"... but the consumers have proven that actually what they want is fun."
    1. Re:Version numbers are meaningless by Spad · · Score: 4, Insightful

      At least Chrome has been consistent about it, Mozilla just seem to have lost it completely when it comes to Firefox, jumping all over the place chasing every new "feature" that one of the other browsers comes up with.

      Seriously, stop trying to be Chrome, Chrome is already doing that pretty well.

    2. Re:Version numbers are meaningless by bunratty · · Score: 4, Insightful

      Chrome uses an extension API to help ensure that extensions work from one version to the next. They also have an updating mechanism that ensures nearly all users have updated to the latest version of Chrome within a week of final release. Firefox has neither of these, so extensions can easily break from one version to the next, and it could be months until most Firefox users update to the latest version. Mozilla should have ensured their updating mechanism worked quickly and most popular extensions used Jetpack before they switched to a rapid release schedule like Chrome has.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
  6. Good for Microsoft by DesScorp · · Score: 4, Insightful

    I hope FF loses some market share. Stupidity should be punished in the business world. I don't personally care if it's Microsoft with IE, Google with Chrome, or Apple with Safari, or any other browser. I don't care about rapid releases. I'm against them, actually. In a business environment, rapid releases only muck up the works and makes life harder for the IT staff.

    --
    Life is hard, and the world is cruel
  7. Re:Do they have an IT dept? by nzac · · Score: 4, Informative

    Firefox 5 is the security update to FF4. I don’t think anything was broken apart from the version number.

    Its just really confusing to people not following this why they would do this way. I was a 5 mb update on windows for me.

    The only change I have seen is maybe a new animation on the left of URL bar (and that might have been there anyway).

  8. Re:Slashdot community's constant hating on Firefox by belthize · · Score: 4, Insightful

    It's not change is bad, it's needless change is bad.

    If Firefox wants to be a cutting edge testing environment for whizbangs great, make that clear. If it wants to be used in production environments where long term stability and available time for internal test cycles trump access to whizbangs then this is bad.

    We use firefox for everything, random websites with new versions of dancing cat videos, personnel apps like timecards, purchasing etc and monitor and control for instrumentation.

    Don't really care if the new dancing cat video works, don't even really care if the craptastic PeopleSoft works, do care that monitor and control stuff works.

  9. Re:Slashdot community's constant hating on Firefox by Spad · · Score: 3, Insightful

    I think most people are just pissed that Mozilla appear to be rather pathetically trying to mimic Chrome of late rather than focusing on improving Firefox where it actually needs improving.

  10. LTS Release? by supremebob · · Score: 5, Insightful

    Perhaps Firefox should take a page out of Ubuntu's playbook, and offer a special LTS (Long Term Support) release that will receive back-ported security fixes for the next two or three years. That will give the IT departments and embedded systems manufacturers the long term stability they want, while general users and browser enthusiasts can continue to update their browser every three months.

    Or they can do nothing, and continue to lose marketshare to Internet Explorer and Google Chrome when IT departments start adding Firefox to their unapproved/unsupported software lists. Their call, I guess.

  11. Harsh Realities by Toonol · · Score: 5, Interesting

    The Mozilla foundation needs to understand that their recent bad decisions have consequences.

    I use Firefox, and have for quite a while. I've gone from a strong supporter and proselytizer to... less enthusiastic. It's still my first choice of browser, but just barely.

    It was the Awesomebar debacle, and their refusal to include an option to turn it off, that first made me suspect they were headed in the wrong direction. Removing the status bar was a bad idea, and then this ridiculous botchup with versioning... sigh.

    They have positives. They have the best plug-in architecture, and they aren't including patented/copyrighted codecs in the browser, which is good (although they should allow a direct interface to the underlying OS codecs, not simply forbid them from playing). Still, I was contemplating shifting over to Opera. Now, today, we learn that Opera is probably going to go to hell in the next few months.

    At this point, I'm hoping that somebody will fork Firefox back at the 3.6 version, and take it from there. It needs to go in a direction the users want, and stop trying to force the users into a direction the designers want. If you stop listening to your users, they will leave. It's beginning to happen with Firefox.

  12. Re:Do they have an IT dept? by fluffy99 · · Score: 5, Insightful

    It really makes me wonder whether these large companies have an IT department.

    Surely they can replace FF4.0 by FF5.0 without exposing their net to Chinese hackers.

    Apparently you've never worked in big IT, where software must be thoroughly tested before being rolled out. Image you're the guy that convinced your company to roll out FF as a replacement for IE and them that it was fully compatible with all their corporate websites. Before you've even fully tested and started deploying it, Mozilla EOLs that version number. Kinda sets you back to square one and you look stupid for having suggested it in the first place.

    Mozilla screwed themselves on this. FF5 is hardly different than FF4, yet yhey bumped the major rev number trying to convince people they are innovating and ended pissed off the corporate customers who want stability. Fedora still hasn't learned this lesson with their 6 month cycle and a hearty fuck you if you don't keep up because you can only safely upgrade from 1-2 versions behind. The corporate world wants stability and good manageability damn it. They don't want a constantly moving target with questionable long term support.

  13. Re:Do they have an IT dept? by Culture20 · · Score: 3, Insightful

    How that's different from an update from the last version of FF 3.6 to FF 4.0?

    Mozilla _just_ EOLed 3.5.x. 3.6.x isn't EOL yet. People expected that the release of 5 would be concurrent with a security patch for 4, because that makes sense. Mozilla showed they lacked sense with the awesomebar debacle.

  14. Re:You had me at... by Anonymous Coward · · Score: 3, Insightful

    Uuum, dude: I had 3 years of psychotherapy after having designed a web app that was supposed to run in IE in fall 2005. This is not a joke. And I have to really pull myself together to not rage and say you should die or something. :/

    I got to know IE extremely well over the years. Every tiny quirk. Even the race conditions depending on a dozen independent factors. Even that horribly illegal code (illegal according to MS too, that is) does not only often work, but in some rare cases even is necessary for it to "work" (this case is also a race condition on top of it all!). And yet I still haven't found the bottom of the pit of chaos, where some inner sense and logic is supposed to be.

    The problem with IE is, that it must have the most advanced AI in human history inside, as it manages to simulate utter irrational and unpredictable behavior with sheer perfection.

    Yes, you can say IE has "improved" since then. But the problem is, that it's still Trident. The engine that is named after a tool of the devil for a good reason. ;)
    It's an utter mess. Calling it "spaghetti code" would insult even the worst spaghetti code any twice-outsourced enterprisey consultant called "The late Paula Bean" could ever write. It just doesn't fit it anymore.

    So apart from a complete rewrite, there is no chance in hell (literally? ;) that it will ever be something even remotely acceptable.

    If MS decides to throw away Trident, we may get a good IE. Until that, anyone who defends IE, just doesn't know shit and never has done some real coding for that monster. And so he should better keep quiet, as every time an IE loads a page, a thousand web developers shiver and shed a tear of past mental rape horror.

  15. Re:Do they have an IT dept? by MrEricSir · · Score: 5, Interesting

    No, the change is NOT only a number. Mozilla has stated that every major version change breaks ABI compatibility.

    That probably doesn't matter to you (it certainly doesn't to me) but if a company distributes Firefox extensions for their employees, they're going to have an upgrade headache on their hands.

    --
    There's no -1 for "I don't get it."
  16. Re:Do they have an IT dept? by fluffy99 · · Score: 4, Informative

    It's only a number and an IT'er worth his salt should be able to confirm that much.

    Yes they can. The problem is that they aren't the ones that make the decision. Large corporations usually have stifling configuration management and strict rules about testing. It's usually non-technical managers that see the new version number as a major upgrade and insist on retesting before they risk rolling it and potentially breaking large number of computers. Yuo should be happy that you're ignorant of this fact.

    About Fedora's 6 months release cycle, maybe you missed Fedora is the cutting-edge development version of and for Red Hat?

    Wow, you were so close to getting my point. Maybe I needed to continue the train of thought just a tad more? Fedora is unsuitable for the corporate desktop for the exact same reason Firefox is. It's not version stable and changes to rapidly. Both products are targeted and marketed to the hobbyist, or environments where a near constantly changing platform isn't an issue.

  17. Re:Do they have an IT dept? by mario_grgic · · Score: 3, Insightful

    That would be true if everything continued to work. But Firefox 5 broke quite a few extensions. In principle I agree that if things just continued to work, then it all comes down to a version number change, and Firefox 5 would be a security update for 4. However, if you also add to the mix that in the "enterprise" a typical user can't do much with their computer, so a simple auto update like this requires admin intervention and you have a real problem.

    --
    As the island of our knowledge grows, so does the shore of our ignorance.
  18. Re:Do they have an IT dept? by symbolset · · Score: 3, Insightful

    The fact that IE9 doesn't run on xp might be a bigger upgrade headache. At least FF5 runs on the commonest OS.

    --
    Help stamp out iliturcy.