How does MIT build any more trust than a copyleft licence like AGPL? At the very least AGPL stops people "stealing" your work without contributing back their changes?

▲

bluGill 2 days ago | parent | next [-]

AGPL does not do anything to force people to contribute their changes back. They have to make the changes available, however that's very different from actually contributing back. It is not hard to make a low quality contribution that the upstream would for very good reason refuse even though it 'works'.

The poster child for this is chromium which is GPL because it has clear and obvious roots in the old KHTML code of 20 some years ago. In theory you can contribute to Google movement and I suppose some people do but realistically Google controls it completely and they will do whatever they want. even though the source is available it is effectively not a contribution back.

▲

RobotToaster 2 days ago | parent [-]

By "contribute back" I was referring more generally to the commons.

The chrome example actually proves my point, the KDE project, or anyone for that matter, can take the changes Google made to their code. If KHTML was MIT it's likely that wouldn't be the case

	▲	bluGill 2 days ago \| parent [-]
		Practically though, there is no difference. The KDE project has lost control over the web browser, even though they started it. It's an all or nothing. They can take all of chrome or they can take nothing. There is no in between. If KDE and Google disagree on the direction of the web browser, Google wins. There is no control. There's no advantage to open source, other than it's free. It may as well be a closed source project for all the good it does.

▲

VladStanimir 2 days ago | parent | prev [-]

You can't be stealing what is given away for free. Developers that choose copileft license want to see al changes shared under the same license. Developers that choose permissive want their code to be of use to as many developers as possible for whatever they want to use it for.