"Ah that means we must remove all security protections, instead of you know further strengthening security."
If older GPL failed, this means we needed a stronger license...such as AGPL, or in future something even better, instead of giving up and saying we should have just given them shit on a platter.
WebKit, the rendering engine that originally powered Chromium began its life as a fork of KHTML a GPL-licensed rendering engine produced by the KDE project for their Konqueror browser.
Its a good thing the GPL stopped google from taking it and running with it!
"Hey we had a security breach!"
"Ah that means we must remove all security protections, instead of you know further strengthening security."
If older GPL failed, this means we needed a stronger license...such as AGPL, or in future something even better, instead of giving up and saying we should have just given them shit on a platter.
Would you mind elaborating? How did KDE's use of GPL prevent Chromium from being closed-source? What about Google Chrome?
WebKit, the rendering engine that originally powered Chromium began its life as a fork of KHTML a GPL-licensed rendering engine produced by the KDE project for their Konqueror browser.
That part I know, but how are you saying that prevented Chromium from being closed-source, and why didn't the same apply to Google Chrome?
8 replies →
Note that it began its life at Apple, not Google. They forked KHTML first as far as i know.
It didn’t: that’s the joke.
You are not aware that chromium is open source?
1 reply →