You said:
Which is why I'm glad to see so many pointing out their doublespeak when it comes to freedom, because for too damned many the only "freedom" you should have is the freedom to do as they say and be like them, no freedom at all.
Not a day goes by, and you say:
because for the pro-GPL crowd it isn't enough that they choose to run only free, its quite obvious from the posts above and below you that they don't want you to have the ability to run anything else.
So, what you're saying is that I should be free to write proprietary software all I want, under whatever restrictions my lawyer can come up with, but should I choose to release the software, that I should not go with a copyleft license.
As my list of projects clearly show, I belong to neither the "Anti-GPL" nor the "GPL-only" camps. As a rule, I try to choose the most restrictive license that does not impose anything on the user of the program (hence - GPL for command line utilities, but LGPL for PgOleDb, which is a driver).
When I have a special interest in people using the software, however, I go with more lenient licenses. BiDiEdit was meant to be a proof of concept reference implementation to a standard, so the higher cause here is the standard, not the actual editor. safewrite represents a relatively modest investment on my part, and a major boon to any program that maintains a configuration file automatically. Since it is a common plague on Linux, my outmost interest here is that people will do safe writes, and my library is a simple convenient way to do it.
The bottom line here is that the licenses on all of those programs represent what I believe is best for my own interests. This is fine and proper, as I am the one who invested the time to write those programs to begin with. You do not gain the moral right to tell me what I should and shouldn't do with programs I write unless you also go around telling Microsoft and Apple what they should with theirs.
Shachar