RE: iSeries 25% Growth 3rd Quarter

One issue I have is generalizing things into categories when it might not
be accurate.  No offense to PC batch file gurus but you would never get me
to say they are similar - except in concept.  And possibly it is the same
with other scripting languages.  I'm not wanting to start a debate on which
scripting/control language is bigger/better/faster than another but I'd be
careful lumping languages into a programming language or a control language
group.

Secondly, if one can make something work in a way that is easy for them and
it's logical and efficient for them - who is anyone to say they are wrong
in doing so?  Again, I'm sure there are plenty of examples of when this
approach has been done incorrectly but I'm betting those are the exceptions
and anyone presenting them won't give you a list of the 99% of the times it
worked, worked well, and saved time.

Thirdly, my attitude is that if someone is in CL - and they can accomplish
their task in this language (programming or control) and it is an adequate
or more than adequate solution - why force them to go elsewhere to finish
the problem?

Fourthly, in a strategic sense while you might want to control
fragmentation why would you want to limit yourself to one solution to a
problem?  And to me fragmentation is an internal issue, arguing best
practices at the language level with a group like this is dealing with
minutia.

Personally I think there is a break down on what language to use where and
that CL's purpose is to work with the environment, associated resources,
and other HLL languages.  But this is an area that is fraught with
exceptions and gray areas.