Re: 5250 to Web Interface / Application Modernization -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: 5250 to Web Interface / Application Modernization
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Fri, 5 Apr 2019 19:44:48 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

In your example, the problem is aesthetics, and the perception of 5250
being outdated. The goal would be to eliminate that problem, most likely
by moving to a web UI.

To clarify my position, I would suggest that adding a "web UI" to a 5250
code base makes the problem worse. Legacy applications need fundamental
architectural changes. Unfortunately, that kind of understanding requires
experience that most legacy developers don't really relate to - until they
gain experience with something better.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: 5250 to Web Interface / Application Modernization , Jack Woehr

This mailing list archive is Copyright 1997-2026 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.