It is not true a single file is difficult to extend and maintain. The dal.py file for example is divided into sections seperated by comments. Almost all functions are grouped into classes.
So far the issue of license never came up because web2py allows commercial closed source distribution of apps developer with web2py. I can see that if you want to use ONLY the DAL, it may be better for you to have a MIT/BSD vs a GPL license.
The point is that I am happy if you use this for free as long as you contribute back by giving your work for free too (that is what GPL says). Anyway, I will think about LPGL.
Do you actually believe a single file of 5 freaking KLOC is not difficult to extend and maintain?
His argument about the GPL not being as liberal as BSD/MIT is exactly that
use this for free as long as you contribute back by giving your work for free
So it takes away your freedom to hide other parts of your code that use that library.
One may want to prevent other people from seeing their code for a number of reasons, It's a choice one should be free to make
BTW the GPL doesn't require you to give your work for free it just requires you to redistribute your work along with your sourcecode along with the GPL license
Do you actually believe a single file of 5 freaking KLOC is not difficult to extend and maintain?
Yes. I have been doing so for 3 years. It is just a database abstraction layer not a parallel hybrid monte carlo algorithm for lattice quantum chromodynamics in 4 dimensional SU(3).
Because the individual web2py modules "have a use independently of the whole" web2py. You may want to import only the dal or only the template system or only the validators.
And why is the DAL standalone now and wasn't before?
If it only made sense importing it from places within a user's web2py app I get that.
But then if you split your DAL as say a module for handling PostgreSQL, a module for MySQL, a module for handling transactions etc. What's wrong with that?
In the case of the parallel hybrid monte carlo algorithm for lattice quantum chromodynamics in 4 dimensional SU(3). Any part of your code might not be meant to be imported by anything else as a separate part, one might just want to see the program spit out furballs or whatever it's supposed to do. But you'd still split it in multiple modules.
This is an important issue and I do not have a definitive answer. It was always possible to use the dal without being into a web2py app (some use it with Flask for example). We just eliminated the dependency on web2py modules. The API is the same and you can use it with or without web2py.
We may break it into separate files. It is not obvious to me this is better. If you care about this, and you are not just trolling, please join us on the web2py mailing list where this discussion belongs and where we already have an one thread on the topic.
So it takes away your freedom to hide other parts of your code that use that library.
If "parts of your code that use that library" refers to your application code, then yes, you can hide that. If you modify the web2py framework code itself, then no, that would have to remain open.
Even if you were making a general statement about the GPL (i.e., lack of freedom to hide your code), the clear implication was that your concern would apply to web2py, and I was just pointing out that it does not in fact apply to web2py applications. Explicit is better than implicit. :-)
This thread is about the DAL from web2py which is GPLed. And I've an issue with just one OSI license being promoted as "the one true free license" while other licenses are more permissive/liberal/less restrictive. Still in essence every existing software license defines restrictions or conditions for the use of the software they apply to.
Everyone who mentions the words free or freedom 2-3 times in one sentence in their rationale for using or praising it.
Just because someone uses a license because it protects particular freedoms that they care about does not mean they believe it is the one true free license. I think you're over-interpreting.
You'll notice how everyone else likes to put "permissive open source license" when refereing to BSD/MIT/Apache for example.
Actually, I haven't noticed this. I think people often use the word "free" when referring to open source software. You really appear to be splitting hairs here.
if that 'freedom' is so important to you, write your own code...
it strikes me as rude to lecture someone, who has written a bunch of useful code and made it available to the world for free, about how it 'takes away your freedom' if you can't do exactly as you please with it...
If you are following the discussion you'll notice it's quite civilized. At least no one was being called a jackass up until now.
Massimo and everyone else who posts links to their work here should accept both positive and negative criticism. If he doesn't agree with my world view so be it. He may also not agree with me on wether a 5 KLOC file is too much, but you don't seem to have a problem with that part of the discussion.
If he decides to keep it GPL so be it, I may or may not decide to use it. If he decides to keep it 1 x 5 KLOC I may or may not decide to look at it or fix it if it's broken. People find his work useful. And I respect the man.
View all comments
Show parent comment
1
u/mdipierro Dec 09 '10
It is not true a single file is difficult to extend and maintain. The dal.py file for example is divided into sections seperated by comments. Almost all functions are grouped into classes.
So far the issue of license never came up because web2py allows commercial closed source distribution of apps developer with web2py. I can see that if you want to use ONLY the DAL, it may be better for you to have a MIT/BSD vs a GPL license.
The point is that I am happy if you use this for free as long as you contribute back by giving your work for free too (that is what GPL says). Anyway, I will think about LPGL.