News for hackers. Stuff that matters.

A comment on Google going its own way, forking WebKit rendering engine. Parent comment

Re:Google going its own way, forking WebKit rendering engine by doe88 on Wednesday April 03, 2013 @06:35PM (#5489718)
@jmillikin

I remember they contributed back to the KHTML project by releasing a patch. Do your employer plan to release a patch back to Webkit? And you also seem to forget that back then there wasn't as many small vendors as there are today. Gecko never was much used outside of Mozilla, which is of course very different for Webkit.

[ Parent | on HN ]
Re:Google going its own way, forking WebKit rendering engine by makomk on Wednesday April 03, 2013 @07:27PM (#5489986)
Errrm, Apple did the bare minimum required by the license of the KHTML code they were using, which was to release the changes they'd made to KHTML as a single blob. It looks like Google has already done more to contribute back than Apple originally did.
[ Parent | on HN ]
Re:Google going its own way, forking WebKit rendering engine by doe88 on Thursday April 04, 2013 @12:28PM (#5493522)
Would be great if they answered this question though https://lists.webkit.org/pipermail/webkit-dev/2013-April/024...
[ Parent | on HN ]