Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

After Google forked WebKit a few months ago into the Blink project the Qt trolls got together and decided that they will basing the future Qt WebKit module on the Google fork of WebKit and not the (Apple maintained) WebKit. While similar the two differ in a few key aspects the main one being if the WebKit/Blink webviews are in process or out of process (ignoring the discussion complication of webkit2).

There were various other reason for following Blink and honestly the day Blink came out I would be shocked if there hadn't been meetings in every company contributing to WebKit putting together a mini-project to decide if they should follow Google. There were a lot of little pain points in the WebKit project and Google in one swoop cleaned up a ton of them. If anything I see WebKit as an example of failing to steward an open source project on the part of Apple or the community as a whole. Everyone was working on their own problems that it was hard to get movement to fix bigger problems that applied to all ports. Even very visible things like letting each port have their own build system sounded good originally, but was one of the things holding the project back. I was on the edge of the community (worked on the qtwebkit port, helped port chrome to linux, ce port, blackberry port, etc) so I know only so much, but it would be interesting to hear from someone closer in the community not about what was bad technically in the project, but how as an project we (socially?) didn't fix them. Why didn't the WebKit meetings fix this? Did Apple have too much say because they owned the svn server to the detriment of themselves?



A little offtopic, but I wanted to clarify to people not familiar with Qt, that the term "Qt trolls" is because the company behind Qt was called Trolltech, before Nokia purchased it.


Didn't google introduce at least some of those "little pain points" due to their requirement for alternate js engine (for v8), and their own process sandbox?

I heard that after the fork, both sides were able to clean up and remove a ton of code (thus benefiting pretty much everyone).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: