Re:Mitigating Memory Safety Issues in Open Source Software
by jsty on Thursday February 18, 2021 @08:03AM
(#26179334)
If all Google wanted was GPL- and AGPL-free code, they're quite capable of assigning their own engineers / contractors to work on it rather than the more tortuous route of going via a 3rd party
[ Parent
| on HN ]
Re:Mitigating Memory Safety Issues in Open Source Software
by bluGill on Thursday February 18, 2021 @08:14AM
(#26179428)
Their accountants probably prefer this route though. They don't get a competitive advantage by have a proprietary license, so open source is a good choice, but the GPL has issues they want to avoid. By going this route they can use tax breaks that are not available for doing the work in house. Sure it is more complex, but the results matter, and the result they are hoping for is someone else does work that they don't pay for.
Re:Mitigating Memory Safety Issues in Open Source Software
by konschubert on Thursday February 18, 2021 @08:23AM
(#26179499)
Also it's probably cheaper to fund an OS developer for a year than paying for lunch alone for their own engineers.
Re:Mitigating Memory Safety Issues in Open Source Software
by jononor on Thursday February 18, 2021 @02:11PM
(#26184134)
What kinds of tax breaks are available for the case of using consultants instead of employees?
Re:Mitigating Memory Safety Issues in Open Source Software
by bluGill on Thursday February 18, 2021 @04:51PM
(#26186169)
It isn't consultants it is 501 charities doing the work. The charity hires the consultants.
There are a lot of tricks needed to make the above work, and details that you need to consult a lawyer and accountant for.
Re:Mitigating Memory Safety Issues in Open Source Software
by enriquto on Thursday February 18, 2021 @08:16AM
(#26179447)
> they're quite capable of assigning their own engineers
but if they develop it for internal usage only, then they don't get the added benefit of destroying the existing copylefted version!