Language Selection

English French German Italian Portuguese Spanish

Open-source divorce for Apple's Safari?

Filed under
KDE
Mac

In an e-mail seen by CNET News.com, a leading Apple browser developer suggested that architects of the KHTML rendering engine--the heart of a browser--consider abandoning the KHTML code base, or "tree," in favor of Apple's version, called WebCore. KHTML was originally written to work on top of KDE (the K Desktop Environment), an interface for Linux and Unix operating systems.

"One thing you may want to consider eventually is back-porting (WebCore) to work on top of (KDE), and merging your changes into that," Apple engineer Maciej Stachowiak wrote in an e-mail dated May 5. "I think the Apple trees have seen a lot more change since the two trees diverged, although both have useful changes. We'd be open to making our tree multi-platform."

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. Two years after hailing Apple as a white knight, those developers are calling the relationship between their group and the computer maker a "bitter failure."

In a conflict some call emblematic of what can go wrong when corporations embrace open-source projects, developers are airing longstanding gripes against Apple, accusing the computer maker of taking more than it gives back to the open-source group.

Apple declined to comment for this story. But Safari engineer David Hyatt did acknowledge KDE complaints in his blog, defending the scope of recent patches and soliciting suggestions on improving Apple's relationship with KDE.

"For what it's worth, the patches I posted...are not solely KHTML patches," Hyatt wrote. "What do you think Apple could be doing better here?"

The subsequent dialogue, played out in public mailing lists and blogs, led to the e-mail exchange in which Stachowiak suggested that the KHTML group start fresh from WebCore.

KDE said complaints about Apple had been brewing for some time, and attributed some of the tensions to the inherently at-odds priorities of corporations and volunteer coders.

"Business is constrained in ways that open source prides itself on not being constrained," said George Staikos, a software consultant, KDE developer and spokesman for the open-source group. "There have been problems all along in the sense that Apple had their own internal issues to deal with (that) did not mesh well with the model used by... continued >>.

More in Tux Machines

today's howtos

Linux-Ready Hardware and Android Leftovers

Red Hat, Oracle's RHEL Clone, and Fedora

Debian and Derivatives: SnowCamp, Debian Gitlab, Debian/TeX Live, Snap Apps

  • Report from Debian SnowCamp: day 3
    Thanks to Valhalla and other members of LIFO, a bunch of fine Debian folks have convened in Laveno, on the shores of Lake Maggiore, for a nice weekend of relaxing and sprinting on various topics, a SnowCamp.
  • Report from SnowCamp #1
    As Nicolas already reported, a bunch of Debian folk gathered in the North of Italy for a long weekend of work and socialisation.
  • Debian Gitlab (salsa.debian.org) tricks
  • Debian/TeX Live 2017.20180225-1
    To my big surprise, the big rework didn’t create any havoc at all, not one bug report regarding the change. That is good. OTOH, I took some time off due to various surprising (and sometimes disturbing) things that have happened in the last month, so the next release took a bit longer than expected.
  • Ubuntu Software Will Soon Let You Install Beta, Bleeding Edge Snap Apps
    No, not TV channels, or the sort the that ferries goods between countries, but development channels, e.g, beta, bleeding edge, stable, etc. Snap developers are able to distribute different versions of their app over “channels”, and have for almost as long as Snappy has been around in fact.