News for hackers. Stuff that matters.

A comment on Introducing Swift. Parent comment

Re:Introducing Swift by andrewtbham on Monday June 02, 2014 @03:36PM (#7835645)
Yeh, I agree. I was surprised when they open sourced webkit. But like you said, it's strategic. I don't think they care that much about the browser. Their emphasis is on apps running in their ecosystem.
[ Parent | on HN ]
Re:Introducing Swift by tsuraan on Monday June 02, 2014 @03:43PM (#7835722)
They didn't have a choice about webkit; it was a fork of KHTML, which was a part of KDE (and available under the terms of the GPL).
[ Parent | on HN ]
Re:Introducing Swift by timgws on Monday June 02, 2014 @08:23PM (#7837415)
Actually, WebKit was a fork of KHTML, correct, but it is licensed under the terms of LGPL. One extra letter, but a world of difference. This is why they had to open source KHTML, but they could get away with not open sourcing Safari (if KHTML was licensed under the GPL, any app that linked against the library would need to be licensed under the GPL, too.)

Let's not forget that webkit when it was released was little more then a code dump - one big patch that had to be applied to KHTML.

[ Parent | on HN ]
Re:Introducing Swift by eduo on Wednesday June 04, 2014 @07:36AM (#7844982)
Also "they didn't have a choice" sort of ignores that they did have the choice of not using khtml and wouldn't have, if its license could've been problematic for them.
[ Parent | on HN ]