Let me clear a few things up here guys, I have
my own iSeries Model 170 I purchased over three years ago (it is up and running
24/7 plus I use it to also host my web site), I purchased all the development
tools plus SQL for the system. I keep it current as far as PTF’s
and am on V5R2M0 of the OS, I keep my skills current. So this isn’t
about me waiting until the business model changes but about not forcing change
down my client’s throat for the sake of change. I agree that
companies that currently employ 20 year old + technology should look at
upgrades (after all it won’t be long and they won’t find anyone
that will have the skills to maintain what they have). But there has to
be a sound business reason to change, these machines aren’t cheap nor is
the software that runs on them. Until something comes along to force that
change it is better to keep them happy and to make sure they know they have
options.
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Klement
Sent: Saturday, February 18, 2006
3:27 PM
To: [email protected]
Subject: RE: [Easy400Group] Re:
ILE RPG or RPG/400
> First off you should only change when the
business model changes (the client
> decides that they need to have a web presence
or some new application
> dictates the requirement for an upgrade).
It's much easier to catch up when you're 1 week
behind than it is when
you're 10 years behind. Common sense, don't
you think?
The same is true of learning programming
techniques. If you're still
coding RPG/400 today, and tomorrow your boss says
"we're going to the web"
you have a LOT more to learn than just web
programming. You have to learn
the differences between RPG/400 and ILE RPG.
You have to learn new column
alignments, larger variable names, date fields,
expressions, prototypes,
subprocedures, static binding, modules, service
programs, activation
groups... none of these have ANYTHING to do
with web programming, but you
have to learn them ALL because you're 12 years
behind the current
technology!
If you were already familiar (even if not 100%
comfortable) with these
techniques, it wouldn't be nearly as difficult to
just learn CGIDEV2 and
get going with web programming.
Even worse, there may be features of the new
language that you don't even
KNOW about that could be bringing lots of value to
your company or your
clients. Things that could make it easier
for you to develop applications
quickly and therefore saving the client
money. Or making your programs
easier to maintain, saving on support costs.
Or making them more
flexible, and therefore bringing extra value to
the customer.
Staying with obsolete technology until you need
some MAJOR change like
going to the web is bad for you. It's bad
for your clients and/or
company. Frankly, it's doing everyone a
great disservice.
> A business could go broke trying to stay on
the bleeding edge of
> technology. This is what is fueling the
open source movement, why
> discard good pc's because gates came out with
vista when you can run
> open source linux and extend the life of the
hardware.
RPG IV was released in 1994. It's hardly the
"bleeding edge" of
technology. It's more than a year older than
Windows 95. Do you hear
people refer to Win95 as "bleeding edge
technology"? Or for that matter,
Windows 98? Many, if not most, places have
completely phased those
operating systems out because their old and
obsolete. Yet, RPG IV which
is older yet is "bleeding edge
technology".
I can certainly understand and agree with the
sentiment of not jumping
immediately on the bandwagon when a new technology
comes out. I'm that
way myself. I'll wait for a year, maybe even
TWO, to see if this
technology is still around and still important.
But 12?! C'mon, Chet!
SPONSORED LINKS
YAHOO! GROUPS LINKS
