Slashdot Mirror


Give Mac Explorer to the People?

An anonymous reader writes "In an article on the BBC News site, Bill Thompson suggests that Microsoft release the source for IE:Mac to the world so that others can continue to develop the product. While this may be a pleasant fiction, Microsoft does seem to be making an effort to change their image. Could we see more OSS interaction from the software giant in the near future?"

18 of 242 comments (clear)

  1. Or not? by shut_up_man · · Score: 4, Insightful

    How about we just let Mac IE die and keep gathering support for Firefox?

    1. Re:Or not? by polyp2000 · · Score: 4, Insightful

      lol, i think you've found the only possible reason that Microsoft might even consider releasing the source code to IE.

      --
      Electronic Music Made Using Linux http://soundcloud.com/polyp
    2. Re:Or not? by vertinox · · Score: 5, Insightful

      Apparently, whoever modded you flamebait never had to use IE for the mac. It is a horrid wretched peice of software that should die like the rotting beast of Golgamathea that it is.

      It is like a program with all the problems and stability issues of IE 5 (sans Active X because there is not Active X for the mac) with none of its benefits that you would get on a PC version. Hell... Most of the pages rendered nothing like their windows counterpart. The program was made from scratch using a totally different team not related to the IE team for the PC.

      As soon as a better alternative came out (Safari) I dumped IE.

      May it burn in hell and let us not metion it ever again.

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
    3. Re:Or not? by steinnes · · Score: 5, Informative

      I agree. IE for mac is buggy, ugly, renders badly, has terrible support for non ascii characters (at least 90% of icelandic webpages that I viewed with it had little diamonds with a question mark inside them, instead of all the icelandic characters). My dayjob is running iceland's most popular website (mbl.is) and trying to keep support for IE:MAC was just a complete nightmare, whilst we could easily maintain correct rendering for Netscape 5+, IE5+ (for windows), Opera 7+, Mozilla 1.4+ or Firefox 0.8+. IE:MAC is terrible violation against the internet, and the notion of extending it's life and furthering the pain and misery it brings down on users is just preposterous. If Microsoft by their own accord want to park this weapon of bad rendering and vileness, please please please lets not give them a game plan to continue! Someone should smack the proposer of this idea on the top of his head for being a big doofus. People should rather focus on making the already better, already open-source browsers for Mac OS better!

  2. You don't wanna do that! by Ochu · · Score: 5, Insightful

    Surely the reason why microsoft would never do that is the fact that not in a million years would that product stay on Mac. I would give it two weeks before it was given enhancements, ported to windows, and released as a compatible alternative to IE 7, eating away at ever more market share.

  3. Why? by badasscat · · Score: 5, Insightful

    The real question is why? The Mac already has both a more modern Apple-produced browser (Safari) that MS themselves recommend, along with a true open-source alternative (Firefox), not to mention all the usual suspects if you're not a fan of either of those (Opera, etc.).

    While it may be a nice pseudo-political irony to have IE Mac go open-source, it is an old, outdated browser that was rendered unnecessary long ago in every sense of the word.

    1. Re:Why? by squiggleslash · · Score: 4, Interesting
      Every time this subject comes up, people make statements about "IE only" sites that Mac IE can access, and Firefox can't.

      Ok, here's the thing: IE-only sites are IE-only for one of two reasons: they've either got stuff on them that only works under Windows Internet Explorer, or they deliberately look for IE in the version string.

      Of the former, relatively few happen to work on IE for Mac. This is because IE for Mac is unrelated to IE for Windows. It's a different code base, written by (apparently) different people, and doesn't work in the same way. (It's possible IE for Mac supports VBScript, that's about the only extra-level-of-compatability I can think of it would have that would help here. Now, how hard could it be to add VBScript compatability to Firefox?)

      Of the latter, many also look for information reporting the browser as working on Windows. And, yes, as you say, it's a lot simpler to fake and/or emulate IE's responses in Firefox than to bring Mac IE up to date.

      --
      You are not alone. This is not normal. None of this is normal.
  4. Well some of the middleware code might be useful.. by MauMan · · Score: 4, Insightful

    I'm not that interested in the browser but some of the middleware code to emulate windows calls on the Mac might be interesting to play with...

    --
    ------- Code to try when you're bored: qsort( 0, UINT_MAX, sizeof( int* ), IntCompare );
  5. Not gonna happen. by Noryungi · · Score: 5, Insightful
    Why? I can list several reasons for this:
    1. If there is something interesting in the code, Microsoft won't release it, because they don't want to help the competition (Firefox or Opera).
    2. If there are huge bugs in the code, Microfost won't release it, because that would be helping hackers.
    3. If IE/Mac and IE/Windows share code, Microsoft won't release it, because that would be even more help for hackers.
    4. Finally, Microsoft won't release the code because that would be helping Apple. And helping Apple (and/or Open Source) is helping the enemy that stands between Microsoft and Total World Domination(tm).


    Not gonna happen. Not in my lifetime anyway.
    --
    The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
  6. free "developers... developers... developers"... by Gopal.V · · Score: 4, Insightful
    If you've seen the microsoft censorship on Everybody Loves Eric Raymond, you'll find this announcment a little disturbing.

    After all from what I understand, Microsoft is looking at exploiting the open source model of development for getting free developers. I very much doubt they would go down a path where they transfer the entire copyright of the codebase to a non-profit organization (like Netscape/AOL and Mozilla Foundation).

    Then again, with Safari working very decently - who needs IE on Mac ?

    I can almost picture Steve Ballmer - "developers ... developers ... developers *aside* heh, suckers"
  7. Oh please, god, no! by Anonymous Coward · · Score: 5, Insightful

    Let it die, let it die already!

    Yes, Mac IE was fairly advanced for its time, but the quicker it disappears from the face of the planet, the better! All the techniques on which modern web design rely that work reliably in all the major browsers have major issues in Mac IE. Floats and clear in particular - these just require such awful hackery when Mac IE specifically needs to be supported... it's worse than IE 5 and Netscape 4 combined! (Okay, so that might be a slight hyperbole.) ;P
    Yes, it's very understandable that the behaviours of these properties weren't well defined back then, and compared to the Win IE of its time, Tantek and team did a superb job with this browser... but that was years ago. It's dead now, and needs to be forgotten as quickly as possible!

  8. Re:free "developers... developers... developers".. by jcr · · Score: 4, Insightful

    Microsoft is looking at exploiting the open source model of development for getting free developers.

    Who isn't?

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  9. Potential copyright issues here by Mister+Mudge · · Score: 5, Interesting

    Microsoft could open-source some of the code - what they wrote themselves - but there's still code in there from Mosaic, which MS licensed from Spyglass. Not sure if Spyglass owns the rights or has just licensed them, but the ownership seems a little murky to me. Does UIUC own it? NCSA? The citizens of the USA, who paid for much of its development?

    I dunno, but I'm betting that MS couldn't easily release IE as OSS even if they were so inclined.

    --
    Mudge

    In theory, theory and practice are the same.
    In practice, they're not.

  10. Re:Well some of the middleware code might be usefu by vertinox · · Score: 4, Interesting

    I'm not that interested in the browser but some of the middleware code to emulate windows calls on the Mac might be interesting to play with...

    There are none. IE for the Mac was built from scratch not using a single line of IE Windows code by a different team of developers who most likley didn't have any formal communication with the IE for windows team.

    --
    "I am the king of the Romans, and am superior to rules of grammar!"
    -Sigismund, Holy Roman Emperor (1368-1437)
  11. Other Suggestions by BodhiCat · · Score: 5, Funny

    Other Suggestions:

    China should withdraw from Tibet and allow the Tibetans to construct a Disneyland in Lhasa, since Tibet is already becoming little more than a tourist trap.

    Bush should withdraw from Iraq and let the war be carried out by our powerful allies from Togo and Lithuania.

    The Road Runner should let the Coyote have him for dinner.

    They should develop a snow ball in hell that would survive for an extended period of time.

    Etc.

  12. Um, no. Just no. by saterdaies · · Score: 4, Insightful

    First, as many have pointed out, Microsoft doesn't have the right to open up all the code.

    Second, the code isn't really worth anything at this point. The rendering engine in Mac IE has nothing to do with the rendering engine in Win IE and it's easily the slowest rendering engine out there (well, it's definitely a ton slower than Moz, IE Win, KHTML. . .).

    Third, the author says that his reason for wanting Mac IE is for some random website that will require it in the future. Unfortunately, while a website may require IE, it won't work with IE Mac. IE Mac has nothing to do with IE Win. It can't run ActiveX. It doesn't render things similarly. If a website requires IE, Mac IE users are out of luck.

    Fourth, I don't think anyone would be impressed by releasing the source for an application that is so dead. Releasing the source for Win IE would be amazing - the community could clean up security holes, improve standards compliance, etc. and make IE a better browser. Mac IE, on the other hand, is long gone. It's just too hopeless to salvage anything useful. It would be like Microsoft open-sourcing Internet Explorer 1.0 - just too old to make anyone care at this point.

    Mac IE is dead. It's old. There's nothing useful there and open-sourcing it wouldn't help the Mac community or the open-source community. It wouldn't give any insight into the things that make websites IE-only since IE-only websites don't work with Mac IE. This article is just bad.

  13. Re:Already dead. by Stonent1 · · Score: 4, Informative

    ...Or Camino

  14. No Vulgar Raymondisms: Users don't review code. by SimHacker · · Score: 4, Insightful

    Please stop spreading the Vulgar Raymondism that the Firefox code is read by millions of users. Have you read it yourself? I'll bet not! Most users and even programmers DO NOT read source code. You only hurt the open source / free software movement when you dump out steaming piles of horse shit like that. There are enough valid reasons to use open source / free software like Firefox, that you don't need to lie about it.

    -Don

    --
    Take a look and feel free: http://www.PieMenu.com