many folks are finding the licensing terms for JUCE-5 to be quite dis-tasteful - but the purpose of this post is not to discuss them but only to point out that the new imposed anti-features only serve to make it increasingly difficult to maintain a freedom and privacy respecting JUCE program
to be clear - although the new terms do not actually state this - what is most likely the case is that all of those new rules apply only to developers who want to release closed-source and not at all to GPL programs developed with JUCE
PLEASE CORRECT ME IF I AM WRONG - and i will stop using JUCE immediately for any purpose and port every JUCE program i have to another toolkit
all it actually says to this effect is: “if you exceed some revenue limit” then “you MUST release YOUR program as the GPL” - what it does not say is: “you may simply choose to take JUCE under the GPL and ignore the rest of these odious terms entirely”
but i do suspect that is still true - unfortunately nowhere in the agreement does it actually say that and o/c none of us developers are lawyers - so the end result is that it is quite disturbing for most of us to read
again i do not care to debate these new terms - i only wish to propose a fork to remove them and the accompanying anti-features for the sake of FOSS developers
JUCE-3 and 4 were already quite a PITA to use properly for GPL programs and for years i have been maintaining a fork that makes JUCE more GPL-friendly - this would be just 2 more anti-features to remove and maintain - but how many more are coming? will JUCE-6 force advertisements on end-users? what will i need to remove next year and the year after that?
the more cruft that must be removed makes for a larger maintenance hassle across upgrades - at some point it will no longer be worth the trouble - so perhaps if some others want to help me maintain a freedom and privacy respecting fork i will continue - but if i must do it alone i will probably just stop using JUCE soon