I'm currently using zope 2.8 with Postgresql, so if you were going to compare it to TG/Django you would have to add the LOC of Postgresql to zope and TG/Django. I'm considering moving to Django, mainly because of its Postgresql/Relational Database orientation. I also believe performance will be better than Zope. Of course looking at a new framework is sort of like the backup quarterback. Everyone wants the backup to start, and then once he does .... Well, lets just say he is no longer the backup QB.
Wow. Those are some interesting stats, but I really don't know what they mean. Yes, it is more useful when you break down the code by category. Also remember that Zope comes bundled with the Zope Object Database (ZODB) for its own data persistence, which is a huge project by itself. TG and Django "outsources" data persistence to a separate relational database like MySQL, PostgreSQL, SQLlite, etc. (I'm curious to see the line count after the ZODB is factored out. Or what TG/Django looks like when you include the loc count of PostgreSQL source.
Regardless, I'm sure there are lots of opinion pieces out in the wild that warn of misinterpreting what loc counts mean. (For example: http://www.martinfowler.com/bliki/CannotMeasureProductivity.html)
(Disclosure: Fowler and I both work at ThoughtWorks.)
But yes, it's good to see Zope3's name thrown into the ring and be part of the conversation/debate/argument/battle royale that defines the Python Zeitgeist.
Comment
I'm currently using zope 2.8 with Postgresql, so if you were going to compare
it to TG/Django you would have to add the LOC of Postgresql to zope and TG/Django. I'm considering moving to Django, mainly because of its Postgresql/Relational Database orientation. I also believe performance will be better than Zope. Of course looking at a new framework is sort of like the backup quarterback. Everyone wants the backup to start, and then once he does .... Well, lets just say he is no longer the backup QB.
Parent comment
Wow. Those are some interesting stats, but I really don't know what they mean. Yes, it is more useful when you break down the code by category. Also remember that Zope comes bundled with the Zope Object Database (ZODB) for its own data persistence, which is a huge project by itself. TG and Django "outsources" data persistence to a separate relational database like MySQL, PostgreSQL, SQLlite, etc. (I'm curious to see the line count after the ZODB is factored out. Or what TG/Django looks like when you include the loc count of PostgreSQL source. Regardless, I'm sure there are lots of opinion pieces out in the wild that warn of misinterpreting what loc counts mean. (For example: http://www.martinfowler.com/bliki/CannotMeasureProductivity.html) (Disclosure: Fowler and I both work at ThoughtWorks.) But yes, it's good to see Zope3's name thrown into the ring and be part of the conversation/debate/argument/battle royale that defines the Python Zeitgeist.