On Friday, 7 February 2020 at 20:44:32 UTC, jmh530 wrote:
On Friday, 7 February 2020 at 19:51:52 UTC, Andre Pany wrote:
[snip]
Now it gets more complicated, GtkD has some additions to the
lgpl rules.
I cannot judge how high the risk is for companies to use this
component, but as an employee I do anything to avoid any risk
for the company I work for.
Kind regards
Andre
The changes are the following:
1) Modification to work on another platform is not a modified
or derivative work
2) Static linking is not a modified or derivative work and you
do not need to include source code.
3) You have to identify that you use GtkD.
If anything, 1 and 2 should make it easier to use GtkD with
your company versus a standard LGPL. The price you pay is #3.
So long as you do #3, it isn't any worse than a normal LGPL
license.
I work in an industry where the goal is to take smart risks and
be compensated for it. Almost everything is a risk. The
question is if the risk is worth it or not. If using GtkD saves
you X more hours a year in programming time than the C API,
then that helps put a dollar value of the benefit. I think the
cost is relatively minor, but that's for your company to decide.
I am in the position to convince the team architect to use an
unknown programming language which gui framework is of type lgpl.
The team architect of course say, why can't we use programming
language x, y or z where there is no license question at all?
From a risk management perspective I would also decide for any
other language just to be 100% on the safe side.
All what you say is completely true. Still, the license makes it
a very hard job to advertise the D Programming Language at the
place I work. It is already hard, and I do not want also get into
discussions with IP department about license issues.
And still, GtkD is in my opinion the best UI for D. If GtkD would
have any other type of license, I could just use without getting
in contact with IP department.
Kind regards
Andre
