[webkit-dev] It's time to remove the Haiku port

Ryan Leavengood leavengood at gmail.com
Thu Nov 3 19:48:30 PDT 2011

On Mon, Sep 26, 2011 at 1:34 AM, Eric Seidel <eric at webkit.org> wrote:
> I think any time the larger community is spending more effort than the
> port authors on a particular port we should be wary about keeping the
> port.

Yes this is totally reasonable.

> Certainly that indicates that either our base-costs for having a port
> are too high (our platform abstraction is poor, etc.) or that the port
> maintainers aren't active enough in the project.

I think it is a little of both. The WebKit platform abstraction could
definitely use improvement, as I'm sure many of you know.

Plus WebKit changes REALLY, REALLY fast. For a project like Haiku
which is strictly open source and volunteer developer driven, it is
hard to keep a port up-to-date.

The fact that so many changes were needed in our files without us
making improvement or changes in our actual port may say something.
Personally I would have told you not to update our files and just let
them be broken if we didn't update them. The fact that so much work is
needed from developers besides the port developers to maintain a more
slowly developing port indicates a problem with WebKit. Well maybe not
a problem, but there may need to be a policy of letting smaller ports
maintain their own files.

On another note, the reply-to on this mailing list is just broken :/


More information about the webkit-dev mailing list