3 ms·
> My hope is that by choosing the MIT license for my bindings, one commercial app in the world will choose to use Qt Widgets instead of Electron I still do t u
by jcelerier 2y ago
> My hope is that by choosing the MIT license for my bindings, one commercial app in the world will choose to use Qt Widgets instead of Electron
I still do t understand this logic. When you combine MIT and LGPL you don't get MIT, you get MIT+LGPL so now you have to take care of both licenses. Electron's LGPL parts don't magically disappear - when you start an Electron app all the things that happen from main() up to executing the first line of your js app code are LGPL
- tracker1 2y agoBecause this library supports dynamic linking, but can itself be statically linked, which is a default behavior for go. Trying to dynamically link a go library that dynamically links, or even statically links to Qt is just an extra level of effort for application developers. This library will be easier for developers to create applications which comply with LGPL of the upstream library without adding additional burdons.