Re: Java is becoming the new Cobol

In article <NoednW8wwYa-heLaRVn_vwA@xxxxxxxxxxxx>,
Scott <NoSpam@xxxxxxxxxxxxxxx> wrote:
THE biggest problem with the mainframe is that IBM never embraced a GUI
screen.

Ummmmm... I was taught, a few decades back, that this wasn't done because
the overhead necessary to make the mainframe architecture do what it
wasn't designed to do (graphic display) would render using the
applications prohibitively expensive. I remember, a few years before
that, being informed that a local Corner Office Idiot had sent out a memo
telling his programmers to reduce their TSO connect-costs... every byte of
core, every swap to disk, all were kept track of and had to be paid for.

I'm not sure how, nowadays, use of a graphics-intensive Linux application
gets costed-out to a department... might be interesting to look into.

DD
.

Relevant Pages

  • Re: Java is becoming the new Cobol
    ... I was taught, a few decades back, that this wasn't done because ... the overhead necessary to make the mainframe architecture do what it ... wasn't designed to do (graphic display) would render using the ... And why is GUI the answer? ...
    (comp.lang.cobol)
  • Re: Java is becoming the new Cobol
    ... Ummmmm... ... I was taught, a few decades back, that this wasn't done because ... wasn't designed to do (graphic display) would render using the ... And why is GUI the answer? ...
    (comp.lang.cobol)