They used to let you sort subscriptions into "Collections", but they removed this feature in 2015. I remember they teased they might bring it back in 2021, but I haven't seen much come of it. [1]
I love the little part with the fake Windows BSOD. The QR code is supposed to link to the documentation page on error boundaries, but sadly it's broken
Yes, there's code in Chromium going back to the KDE/ Konqueror and WebKit days that's LGPL licensed. Mostly in the Blink rendering engine like you linked.
You really should not use this ever in any situation, but for historical reasons[1], if they are the only thing on the line you can use HTML comments in JavaScript like so:
function foo() {
<!--- returns true ---->
return true;
}
This works at least in Chrome and V8, not sure about Firefox.
Also, Chromium's Blink renderer has a lot of LGPLv2 source files that date back to the KDE KHTML days[1] and as you can see by the numerous proprietary applications that use Electron and Chromium Embedded Framework, that this doesn't hinder companies from using LGPL libraries as long as they abide by the license.
However, one thing to note: the OSS version of Qt uses the LGPLv3 license, which has additional restrictions (like the "Anti-Tivoization" clause) which make it incompatible with the iOS AppStore thus forcing you to use the commercial version of Qt in those situations. Not sure about the Mac and Windows 10 app stores, I am curious if anyone knows/has experience with LGPLv3 and those stores?
> which make it incompatible with the iOS AppStore thus forcing you to use the commercial version of Qt in those situations.
Not necessarily. If you're able to distribute versions of your app to iOS users so that they can link it against their own Qt libraries, you'd be in compliance with the LGPL.
I've seen companies that distribute via the App Store, but also provide object files with instructions to link them against user supplied Qt libraries and to get them on iPhones/iPads.
The build scripts and the JS files in the project that interact with FFmpeg and give it a JS API are licensed under the MIT license, but FFmpeg itself is still LGPL.
[1] https://www.youtube.com/watch?v=qGSHPhR8k8g