RE: FW: IBM's RPG Strategy (was: Long Procedure Names)

> From: David Morris
> 
> Something is wrong if Java crashes frequently on your system.

I agree.

> From: Scott Klement
>
> ...If portability is your primary objective, then Java is a good
> language.
> That's really what it does well -- and frankly, it's all it does well.

Java, as all OO languages, works best in a relatively static solution
set.  Mathematically speaking, the less your model changes, the better
OO performs.  In particular, OO languages are EXCELLENT at translation,
such as translating between the many variations of ML (HTML, XML, WML,
you name it).

Also, if you can define a base set of functions underlying your business
application (such as converting to and from a specific display format,
or having pageable lists, or editing children of a parent), then you can
take advantage of OO.

Thus, I find Java to be a premier language for developing thin user
interfaces (because it's primarily an issue of translating to HTML).
And once I settle on a rich client interface, my applications will
instantly have that interface available.

At the same time, RPG is the best language I have ever worked with for
defining data-driven business rules.

Joe