My comment wasn’t written with enough precision.

Using GPL software: yes. Totally fine. The rise of Linux and all that jazz.

Incorporating any part of GPL software _into_ other products? Pretty much doesn’t happen. Every company I’ve ever worked for has said “do not bring LGPL or GPL software into the codebase.” When it comes to commercial software, be it cloud based, or downloadable, you’re not going to find much that tries to incorporate GPL stuff. You just won’t.

▲

anikom15 5 days ago | parent [-]

Of course proprietary software products aren’t going to bring in the GPL. They literally can’t.

▲

apgwoz 5 days ago | parent [-]

They _literally_ could.

▲

anikom15 4 days ago | parent [-]

How does one keep software proprietary while leveraging the GPL (aside from the case of not distributing it)?

▲

apgwoz 4 days ago | parent [-]

There are a few avenues.

1. You incorporate GPL software and hope that no one notices and/or no one challenges. This is the most popular approach, and it’s quite successful, actually. 2. You cease to be a proprietary software company. Less popular, but an option.

Both of these are literally possible.

▲

anikom15 3 days ago | parent [-]

1 is a breach of license, 2 is not a solution to the problem, it is avoiding the problem.

Plenty of companies develop both proprietary software and contribute to GPL codebases. It’s not at all the dichotomy you think it is.

	▲	apgwoz 3 days ago \| parent [-]
		Just because it’s a breach of license doesn’t mean it doesn’t happen… Plenty of companies also don’t allow their employees to contribute to GPL tools with company resources.