What we're finding is that games are taking over a lot of serious
applications. Flight simulators are an obvious example.
The last I checked (admittedly a good few years ago) the commercial
flight simulators were *very* different beasts to the flight sim games.
For a start, they used several computers for one flight simulator,
secondly they did not have a GUI, all the interfacing being via real
aircraft controls
3d graphics are
increasingly being used for other non-games, for instance to produce
architectural models.
I would be surprised if 3D CAD did not predate 3D games.
Then games and mobile phone apps are beginning
to merge. Finally, millions of consumers have a games console as their
only general-purpose computer.
A games console is not a general purpose computer, it is a very heavily
targeted computer.
However people aren't going to stop playing video games, and we have a
fun environment in which to work.
However most computers will continue to be without GUI interfaces
because most will continue to have no display at all.
To get back to whether there is much done with just stdin/stdout/stderr
interfaces, on computers used for serious work (such as running the
financial applications for some big companies) there are a host of
administrative tasks performed by automation scripts which rely on
programs accepting input from stdin and sending output to stdout. Such
input/output streams being redirected and, when appropriate, the output
being fed in to the input stream of a command line mail client to let
the administrator know there is a problem.
Also command line tools are far better (so the support staff tell me)
when you have to log on to a machine across the internet or a dial up
and fix things.
These tasks may not be what the majority of PC users do, but they still
account for a lot of the real work done on computers.