I'm organizing a Django users meetup in Palo Alto (CA) on April 27th.

If you live in the area and want to meet up with other Djangonauts  
(over free food!), check out the details at http://www.jacobian.org/
2006/apr/12/django-meetup-palo-alto/ and let me know to expect you  
there.

I'm hoping to get a chance to meet a bunch of people from the  
community and talk about Django; I hope you can make it.

Jacob

I'll be there IF it's on Thursday, April 27 (as mentioned in your mail to the
django-users list). If it's on Wednesday (as mentioned on your web page), I
won't be able to make it.  Please clarify this.

You might want to post the announcement to the "BayPiggies" list, too.
Django's frequently mentioned at our Piggies meetings and I suspect there are
a few Django users that monitor their list:
http://baypiggies.net/

Best,

Eric.
--
_________________________

Eric Walstad
740 Clementina Street
San Francisco, CA 94103
415-864-4224 voice & fax
e...@ericwalstad.com
_________________________

Thanks again,

Jacob

Thanks very much for organizing, and paying for, the dinner last
night. It was a pleasure meeting you and the other guys that showed
up. I enjoyed the lively conversations.

At dinner I mentioned the application that we recently rolled out, the
California Instant Rebates application
<http://cainstantrebates.com/>

One of the guys asked about it wanting to know how many source lines
of code.  I didn't mention last night that this app was a ground-up
rewrite of version one of the application, which was written (by
others) in Java/J2EE.  Here's a sloc comparison summary:

Java version:
23,150 lines of java code
16,090 lines of jsp code
=========================
39,240 lines of code total
(no documentation, no unit tests)

Python version:
14,928 lines of python code*
 3,677 lines of unit test code
 6,376 lines of django templates
=========================
24,981 lines of code total
*(includes plenty of doc strings)

Now it's not really a fair comparison because the Python version has
more features than the Java version did and it was designed by
another team.  The Python version is also much easier to debug
because of the unit testing framework, documentation and sane design.  
All things considered, this app has been a huge success for me, my
team and our clients.  Three cheers for Python and Django!

Eric

could you be a bit more specific about what kind of "J2EE" the
application was originally written in?

Was it using Struts, Spring, EJBs (which version), Hibernate, JSF...?
Or Just plain old JSPs+Servlets?

  S.

j2ee 1.3 - No struts, nor spring.  EJB's mixed with servlets and jsp.

For the sake of clarity, I should say that the Java version did have some
documentation strings, but they were implemented inconsistently and often
contained cut-n-paste type errors.  For example, the documentation for one
class might refer to different class.  So, the java sloc numbers include
*some* documentation, often useless, very sparse.  Probably less than 10% of
the java classes/methods had doc strings.  I'd estimate the python code has
doc strings in over 95% of the classes/methods/functions.  I use epydoc to
generate API documentation for the application.

-E