toggle

AAPL Stock: 102.5 ( + 0.25 )

Printed from http://www.macnn.com

Apple considers abandoning KHTML for Safari

updated 09:55 am EDT, Thu May 12, 2005

KHTML and Safari

Apple has proposed resolving compatibility conflicts in Safari by in favor of its own WebCore. In an e-mail cited by CNET News.com, leading Apple browser engineer Maciej Stachowiak suggested that architects of the KHTML rendering engine consider abandoning the KHTML code base, which Apple has used for the last two years. The suggestion, which KHTML developers said they were unlikely to accept, comes as Apple tries to quell rising dissatisfaction among the original architects of KHTML. These developers are calling the relationship between their group and Apple a "bitter failure," accusing the computer maker of taking more than it gives back to the open-source group.




by MacNN Staff

POST TOOLS:

TAGS :

toggle

Comments

  1. Monstermind

    Joined: Dec 1969

    0

    The evidence mounts...

    ... Apple is becoming Microsoft.

  1. garmonbosia

    Joined: Dec 1969

    0

    RE:The evidence mounts...

    Actually, it could just as easily mean that Apple is responding to market realities, and the KHTML group is being dogmatic and slow. Imagine that.

  1. udecker

    Joined: Dec 1969

    0

    Read the Article

    The actual email they quote seems to imply that KDE and KHTML developers should use WebCore instead, since they believe that Apple hasn't "given back" enough. The developer states interest in making WebCore multi-platform. This headline isn't entirely accurate.

  1. cmoney

    Joined: Dec 1969

    0

    OSS dogmatic and slow?

    Say it isn't so! That can't be true.

    I wouldn't be surprised if the problems could be a result of Apple wanting to satisfy the regular normal folk and KHTML group not really caring much about them and wanting to make something great for themselves. That's one of the biggest failings of OSS IMHO.

  1. chris409

    Joined: Dec 1969

    0

    Good news to me

    If replacing KHTML with WebCore results in a better browser, then more power to them. Apple has knack for creating software that just works.

  1. solbo

    Joined: Dec 1969

    0

    OMG, are people retarded?

    WebCore is basically a fork of KHTML with a lot of improvements by Apple. They have already abandoned pure KHTML.

  1. Jonas Maebe

    Joined: Dec 1969

    0

    Re: OSS dogmatic and slow

    From what I understand, it's not about "satisfying the regular normal folk" vs "making something great for themselves", but about "incorporating quick but dirty fixes because the next OS release needs a Safari with lots of new features" vs "keeping the source clean and maintainable".

    I.e., deadlines of a commercial company vs making code as maintainable as possible so that people who only work on it in their spare time can work as efficiently as possible. That's not a failing of OSS, it's simply different priorities.

    And I think in the long run, consumers also benefit from cleaner code (just look at the switch from the big hack that Mac OS 9 became to the cleaner Mac OS X code base). I do not think clean code and even short term commercial interests are mutually exclusive though, but it does take some discipline.

  1. trevc

    Joined: Dec 1969

    0

    WHy?

    Why wouldn't Apple consider using the gecko engine. Just based on it's larger marketshare than Safari.

    Unless I'm missing something, it'd bring more compatability and would be a very positive move?!?

    I always thought that they should of done that from the start...

  1. solbo

    Joined: Dec 1969

    0

    Gecko is bloated

    It is extremely bloated and the code does far more than Apple would need.

    KHTML was extremely streamlined when the decided to use it. It is just the rendering engine and there is the Javascript part.

    The Gecko code base is huge and complicated. Not even a lot of the developers know all the workings of it. It is tied to the other Mozilla technologies that make it more of a platform than an engine. Separating Gecko from the rest would be a ton of work and would probably take some serious rewriting. The better question is "Why would they go with Gecko?".

  1. trevc

    Joined: Dec 1969

    0

    re:Gecko is bloated.

    Now I know the 'rest' of the story.

    I thought compatability with bank sites, etc. would improve, but it sounds like stuff like javascript would be different, but I'd think the DOM would be the same and support for different CSS, etc. which causes some of the compatability problems???

Login Here

Not a member of the MacNN forums? Register now for free.

toggle

Network Headlines

toggle

Most Popular

MacNN Sponsor

Recent Reviews

Kanex KTU10 Thunderbolt to USB 3.0 and eSATA

Apple has never been shy about funky ports -- first it was Apple Desktop Bus, and its own DIN-8 serial port. Following that came FireW ...

Logitech Hyperion Fury mouse

Selecting the correct gaming mouse comes down to finding a device that balances the needs of a user with a price they can afford. Ofte ...

Life n Soul BM211 Bluetooth speaker

Bluetooth speakers aren't only for listening to some music at the park or on a long bus ride, but can also be built with tablets in m ...

toggle

Most Commented