> However, I also think it's fairly easy to circumvent for a hypothetical leech that just wants to use my code without contributing back any improvements. Namel

> However, I also think it's fairly easy to circumvent for a hypothetical leech that just wants to use my code without contributing back any improvements. Namely just put the improvements into a separate proprietary file, and insert stubs in the MPL licensed file calling the proprietary code. Yeah this is the work around that came to mind when I first read the MPL, and it's what I had in mind when I said it isn't perfect. I'm using it for a current game engine project I'm working on, and will probably use it for any of my other work moving forward, but I definitely think it isn't the end of license history — there is still a lot more improvement that could be made. I was just giving it as an example of what I think the correct direction is, in contrast to the current extremes. I think it's where more work on licenses should go.