× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Software life cycle - was IF ACTIVE
  • From: "Kevin Palmquist" <kevinpalmquist@xxxxxxxxxxx>
  • Date: Mon, 11 Jan 1999 15:15:15 PST

In my heart, I am in agreement regarding modernizing apps but there is a 
"CATCH-22" for AS/400 evangelists:  one of the big points made in 
marketing the AS/400 is it's ability to help a company retain it's 
investment in software.  So we need to be careful to balance our desires 
for progress against (at least one of) the strengths of our platform. 
 Lest I sound like an ultra-conservative "stick-in -the-mud" I have to 
admit that I am in the process of playing with Domino, learning Java, 
trying to convince certain folks to consider web-enabling their apps, 
etc.  I just wanted to present a little food for thought.  I also think 
I may have just set a new midrange-l record for cliches contained in a 
posting.  We're number one!

Kevin Palmquist




>From: Buck Calabro/commsoft<mcalabro@commsoft.net>
>Date: Mon, 11 Jan 1999 14:09:04 -0500
>To: MIDRANGE-L@midrange.com
>Subject: Software life cycle - was IF ACTIVE
>Reply-To: MIDRANGE-L@midrange.com

>Have you considered rewriting your apps to take advantage of the native 
>environment?  I've been through too many conversions to keep quiet on 
this. 
> Converted code has the advantage of being up and running very quickly.  
It 
>also has the disadvantages of being fragile, hard to maintain and 
difficult 
>to upgrade.  It also freezes old application design into "new" code.  
Brand 
>new code can take advantage of the native environment in a way that 
>converted code never could, and you get to modernise your _application_ 
as 
>well as the code that makes it up.
>
>This is exactly how a 1975 application (batch entry, load a work file, 
>sort, print, update) stays an integral part of a 1999 software package. 
>This is exactly how a midrange programmer in 1999 has experience with 
MR 
>but not embedded SQL, which the rest of the world has been using for a 
>decade.  Old code should be allowed to die after some point - if it 
gets 
>too bad, it gets replaced by a package because the rewrite cost is just 
too 
>high.
>
>I apologise to all for the rant, but would appreciate comments on how 
>others perceive the software life cycle.  How many applications 
designed in 
>1975 do *you* think should be running today?
>
>Buck Calabro
>CommSoft, Albany, NY
>mailto:mcalabro@commsoft.net
>


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.