Slashdot Mirror


Mozilla Project Hurt by Apple's Decision to use KH

Anonymous Coward writes "I Read this article from ZDNet claiming how some of the Mozilla developers were hurt by Apple's decision to use KHTML over Gecko. I can see both their points. Mozilla was made for cross-platform compatibility, and this probably adds to the bloat, however that's not what they were looking for. They wanted small and fast."

5 of 610 comments (clear)

  1. abandon ship by spongebobsquarepants · · Score: 1, Troll

    Maybe it's high time to put Apple in the back of our minds when it comes to open source development. Let's face it, they generally slow the process down (e.g., OpenOffice) or try to re-invent it (X11) and hide behind more restrictive licenses after borrowing from the wealth of open source code (...though kudos to them for their recent contribution to the Konqueror project). Let Apple take the responsibility for streamlining code to work under their platform.

  2. Bah.. Mac users will still use IE by Anonymous Coward · · Score: 0, Troll

    Interent Explorer is still the best browser for the Mac platform. By Apple getting rid of it, its a big slap in the face for users of OSX.

    Oh well, Apple is only 3% market share, so who cares anyways?

  3. Consider the source: Ziff Davis by Spoing · · Score: 2, Troll
    Regaurdless of the personal feelings of Mozilla developers, ZD is known for this kind of sensationalistic and emotion-charged reporting.

    Ziff Davis wants you to jump on this -- and visit thier site. DON'T DO IT!

    That said, Apple and Apple's staff can choose what they wish or what fits the task. If they decide later to use Gecko for something else, ZD will no doubt run a "Apple uses Mozilla -- KDE developers miffed!" or some such garbage.

    The important thing is that open source is becoming more and more important on the user end -- not just on the server side.

    --
    A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
  4. Re:Why hate KHTML? by bricriu · · Score: 1, Troll

    Because KHTML supports CSS like tissue paper supports wet bricks.

    KHTMLs CSS Level 2 compliance is for crap. Gecko's, by contrast, is fully up to spec.

    --

    AHHHHHHH! I'm burning with goodness again!
    - Reakk, Sluggy Freelance

  5. Re:Nothing new here by DrXym · · Score: 0, Troll

    And all of the above have visible menus and buttons that tie in to .mac, to buy CDs / airline tickets / hotels / movie tickets through Apple partners, to listen to their radio stations, to sync with an iPod etc. So they use open standards to direct people to their proprietary services - so what?