[tolmasky]

Sure, but the whole point is that the parties choosing to adopt "Source Available" licenses are doing so because they failed to predict how their users would use and profit from it, and in response, are wanting a new arrangement that better benefits them. So in some sense, we know ahead of time that this is a group which has been upset by unexpected use of their software. Now they've created a license that specifically gives them the benefit of the doubt in such scenarios in the future (vs. MIT which gives that benefit of the doubt to the user). As such, I as a user would be entering into an agreement that specifically is weighted against me in a case that has happened before, with a party that has shown in the past to want to change the rules when they felt they were not being sufficiently compensated. This makes me feel significantly less safe without the presence of a lawyer than with a license that has lots and lots of example usage. Would you say that's fair?

[Drdrdrq]

Fair to the user - less than with FOSS, but more than with proprietary licenses. Fair to developer, yes.

But the problem for me is that if developers don't have incentives aligned with their users', then we get low quality software. I am a FOSS user and have been for many years, but while I appreciate the freedoms it grants me, the whole experience is... Let's say "inconsistent". I would prefer limiting some of the freedoms in exchange for better software, and especially in exchange for having it at all on mobile.

I think the somewhat extreme view FOSS movement holds about freedoms actually hurts opensource adoption, because it hurts its quality and availability.

Note that I don't mind Amazon (ab)using FOSS so much as I mind not having any freedom on mobile.