Linked by David Adams on Sun 6th Nov 2011 04:35 UTC, submitted by twitterfire
Permalink for comment 496208
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2008-08-19
For enterprise apps, it's *extremely* convenient to do it that way. A lot of those apps have their roots in ancient "green screen" apps - once used via a genuine dumb-terminal, later via some sort of terminal emulator under Windows.
And when you have a software company with a lot of experience developing under Unix systems and clients with a lot of experience running those same systems, then adding a Unix-based web layer on top of those apps is the obvious way to go. The first step is probably a collection of Perl CGI scripts that screen-scrape the old terminal app, and which over time evolve into something more sophisticated. This kind of thing is probably a big part of why Java was so successful as a server language - it came out at just the right time for companies looking to replace their old green screen apps.
(And yes, speaking from experience here...)