Search Results
8/3/2025, 2:19:48 PM
>>106122373
I used to work for a company that would convert old green screen applications into web apps. In nearly every case, the people who had been using those systems for a long time hated the new web app because it took so much more time to do anything. The green screens loaded up quickly and buffered keystrokes so for certain workflows, they could get several screens ahead of the monitor even if the screens loaded quickly. That's not doable with a web apps, or at least not using standard development patterns.
Even though the old systems worked well, management wanted a web based replacement because it was easier to train new (low cost) employees on it and made the company less dependent on long term employees. The web apps were also easier to maintain since there's no shortage of web devs but people who can write green screens, usually in something like COBOL or Sculptor, are expensive and booked up well in advance.
I used to work for a company that would convert old green screen applications into web apps. In nearly every case, the people who had been using those systems for a long time hated the new web app because it took so much more time to do anything. The green screens loaded up quickly and buffered keystrokes so for certain workflows, they could get several screens ahead of the monitor even if the screens loaded quickly. That's not doable with a web apps, or at least not using standard development patterns.
Even though the old systems worked well, management wanted a web based replacement because it was easier to train new (low cost) employees on it and made the company less dependent on long term employees. The web apps were also easier to maintain since there's no shortage of web devs but people who can write green screens, usually in something like COBOL or Sculptor, are expensive and booked up well in advance.
Page 1