Michael Jouravlev wrote:
On 11/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Anyway, now we're moving to a new J2EE development environment and trying
to decide how to build apps going forward Struts is the logical choice
because we know it. However, one of the big issues we have with Struts
right now is that it still involves a lot of things to be done "by hand". I
don't mind but management keeps coming back at us with "how come the .NET
group can crank out the webapps so much faster? Why do you have to build
all these common components? Why does it take so long? blah, blah, blah"
Why don't you (your team) just switch to .NET? This is not a sarcasm.
Are you allowed to say that? ;)
Michael has a good point: if you're changing infrastructures anyway, and
you already have an in-house .NET knowledge base, what is the compelling
reason to stay with J2EE?
An why _does_ it take "so long" for your J2EE team to build
applications? That's a legitimate question that you'll have to answer. I
have no ability to purchase tools at this time, but by spending a small
amount of time with a decent language (I use Ruby and/or Lisp) you can
often automate large chunks of previously hand-driven stuff. For
example, I run a ruby script to add an action to a webapp: it adds the
action mapping to the struts config, creates some default things in my
app resources, creates a JSP tile chunk and creates a tile definition,
etc. There's still stuff to do, but not as much as before, and it keeps
you from forgetting Really Important Stuff.
Believe me, I have little love for the .NET development experience
(although C# is pretty nice as "normal" languages go) but...
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
