RE: Getting to the bones with Java and .NET was ->RE:RE: WDSC and Linux

> From: Mark Phippard
>
> For those of us that are not on those other lists, care to fill us in some
> more on what you guys are talking about?

The basic discussion is about the .NET vs. J2EE.  Aaron's position is that
J2EE is too much hassle, too hard to learn, and too much work, and that .NET
allows you to do everything you need to do very easily.  My counterpoint is
that I feel J2EE and especially the JSP Model II architecture is more sound
than .NET, and better in the long run.  Obviously this can quickly escalate
to religious fervor stage, and Aaron and I managed to get there pretty
quickly.

However, once we calmed down and stopped throwing brickbats at one another,
it became obvious that this was a serious topic that needed some objective,
empirical evidence.

We don't know what will happen.  Aaron comes from the brave new world of
plug'n'play, and cranking out applications is his mantra.  I'm old school: a
design, architect and deploy kind of guy.  I like an inhouse architecture
flexible enough to stand additions, while Aaron like to take stuff that's
already available and put it together in response to user requirements.
It's traditional development vs. extreme programming, open systems vs.
proprietary integration (and being an iSeries guy, it's funny that I'm on
the open systems side of this argument <grin>).

We thought it would fit here, though, because anyplace that Visual Studio
has an edge over WDSC is something for Phil's team to at least take note of.
And while Aaron has the full blown Studio at his disposal, I'm going to play
with the new ASP.NET Web Matrix (the free subset of VS.NET), and see what it
has to offer.

Joe