An alternative strategy might be a dual license: a GPL version and and a commercial version. Of course, this model seems only a good option if your software is going to be used in other commercial products (like Trolltech's Qt is an excellent C++ library used in other commercial software). I really doubt if that would work for end-user products like a text editor...
Personally, I am a Belgian, and I am actually wondering why our newspapers just don't apply the same protection like, e.g., IEEE
on their journals. You often get a Google hit to an IEEE paper on the IEEE server, but you then get the login page. Without password, you can't get access to the content.
Of course, the copyrighted contents of IEEE is in the form of pdf's. Is it so much harder to protect html pages than pdf's?
Slashdot Mirror
An alternative strategy might be a dual license: a GPL version and and a commercial version. Of course, this model seems only a good option if your software is going to be used in other commercial products (like Trolltech's Qt is an excellent C++ library used in other commercial software). I really doubt if that would work for end-user products like a text editor...
Personally, I am a Belgian, and I am actually wondering why our newspapers just don't apply the same protection like, e.g., IEEE on their journals. You often get a Google hit to an IEEE paper on the IEEE server, but you then get the login page. Without password, you can't get access to the content. Of course, the copyrighted contents of IEEE is in the form of pdf's. Is it so much harder to protect html pages than pdf's?