RE: Java vs .NET was: RPGIII compiler vs Visual Basic

>I still don't get the "simplicity" argument. 

Let's remember too, many of us are looking are code that is
intentionally generic, as many of us write applications for sale. If
it's an internal application where you're in control of the environment
life gets even simpler.

This is real code from an application of ours that services 5000+ users
over 12 databases. Based on who you're logged in as you have different
connection strings to the databases, and those are based on rows in yet
another table in another database. As the end programmer, to connect to
the correct database, run a stored proc passing it a parameter and get a
result set I would write: 

SqlDataReader dr = IRBData.ExecuteReader("usp_GetContactsForMerge",
MergeFromContactGUID);

The IRBData object encapsulates all the code necessary to figure out
where to go, connect to the database, run the query, close the
connection and return the results. 

My point isn't that this is unique to .NET, it's not. My point is that
with some forethought even something as "simple" as what you and Steve
have posted can be simplified to the point of being trivial -- and
that's what I like, trivial code!

-Walden

------------
Walden H Leverich III
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)