3 ms·
I think this are good news for WebKitGtk. I wondered about the license because they had already problems with LibWebTRC which uses BoringSSL (BSD-License). Ski
by ho_schi 3y ago
I think this are good news for WebKitGtk.
I wondered about the license because they had already problems with LibWebTRC which uses BoringSSL (BSD-License). Skia seems to use the new BSD-License without the advertising clause and is therefore compatible with the GPL.
PS: As valleyer mentions - this affects WebKitGtk not all WebKit ports? At least Skia is usable on MacOS/iOS.
- sph 3y agoFor others that didn't know about this advertising clause: https://www.gnu.org/licenses/bsd.html https://www.gnu.org/licenses/bsd.html
- thrwwycbr 3y agoI think they try to unify their rendering workflow, just like chromium did when they forked off blink and switched to skia. In WebKit, however, that implies that they refactor the Bridge API that is used in between contexts and processes which was an internal API before and broke away often. So I'd guess they start to do incremental changes on the Web API implementations first before they break too much anywhere else (e.g. sidebars, UIs, widgets, devtools are rendered differently but rely on the very same Bridge API)