Fwd: Re: [Calendula-devel] Architecture Thoughts: J2EE vs Python

[Tom Panzarella]

From: Tom Panzarella <tpanzarella@mac.com>
TO: Jason Maas <maasj@dm.org>
CC: 
Date: Sat Apr 03, 2004 10:40:33 PM EST
Subject: Re: [Calendula-devel] Architecture Thoughts: J2EE vs Python

>
>let's get back to the point at hand...
>
>>Could we port that over to J2EE?
>
>I'm not sure I understand your point here.  Are you saying here that by
>predominantly using Python the Calendula project is destined to poorly
>reinvent J2EE?
>

No. What I am saying is that J2EE has already addressed many of the issue that Calendula will have to face.  Starting from "scratch" is hard.  J2EE is nothing but a set of API specifications that addresses all of the "known" issues that are common to distributed apps.  The implementors of the J2EE spec (be it BEA, IBM, or JBoss) have already built the plumbing necessary for application developers to focus on their application specific needs.  I don't know of anything in the Python world that is nearly as comprehensive or robust to even compare ... So.... if the implementation of Calendula is in Python, many of the same concerns already addressed by J2EE will have to be considered by the Calendula developers.

>
>Also, I didn't totally understand your response to Matt's question
>(paraphrased): "if you think J2EE is the best way to go, why are you
>so gung-ho about Python?"  
>

Because the project manager, Darryl, has declared it his choice.  He is very smart in doing this.  He is comfortable with Python and it's capabilities.  If everyone else were to "quit" tomorrow, he would still have a workable code base in his lap.  There is much more to picking a platform and architecture than pure technical merits ... one must take a pragmatic view when heading up a project such as Calendula.

>
>Are you saying that it's because you enjoy the
>challenge of "doing it all yourself"?  
>

No, but it can be fun -- but I'm not interested in Calendula to "reinvent the wheel", I am attracted to this project because it will help NGOs ... a business sector that I hold very close to my heart.

>
>Or is it because J2EE is what
>you do "at work" 
>

Partially ... although, even though I work primarily in a J2EE environment, I still love Java programming -- the innovation in the Java community is unrivaled compared to what I have seen elsewhere ... again, just an opinion.

>
>and Python is what you do "for fun"?  I'm a bit confused.
>

Good question.  I actually haven't done anything in Python that I would consider *real* in a very long time.  I use Python (and Perl and /bin/bash ... depending on my mood) to do the little "hacks" that I need on a day-to-day basis -- because that is what I am good at using those languages for.  Currently, what I am doing for "fun" is Groovy (http://groovy.codehaus.org/) programming.

t.