Comment Re:Why? (Score 1) 618
I'm pretty sure the weakness goes all the way down to th protocol. A remote X client program wouldn't be able to accomodate significant differences between two different servers, should such differences exist (screen size, color map, etc.). The X server can be thought of as a 'thin client' but very complex, it's behavior being closely tied to the hardware configuration on which it's run.
Screen, and any apps the user may run under it, are all 'server side', requiring only a thin client (a basic terminal emulator and ssh or telnet) on the remote end(s). Little accomodation need me made at the server side, simply because it has low expectations to begin with.
My "neterotextual" desktop includes screen, BitTornado (buttorrent), muttella(filesharing), centericq (IM), mutt (mail), pal (calendar), tdl (to-do), sclj (livejournal client), w3m (web browser), wget , ncftp, netcat, bash and vi. I've been looking at using a combination of blosxom and some wiki software for keeping prgress notes and such; bryar is looking very good at this moment.
Screen, and any apps the user may run under it, are all 'server side', requiring only a thin client (a basic terminal emulator and ssh or telnet) on the remote end(s). Little accomodation need me made at the server side, simply because it has low expectations to begin with.
My "neterotextual" desktop includes screen, BitTornado (buttorrent), muttella(filesharing), centericq (IM), mutt (mail), pal (calendar), tdl (to-do), sclj (livejournal client), w3m (web browser), wget , ncftp, netcat, bash and vi. I've been looking at using a combination of blosxom and some wiki software for keeping prgress notes and such; bryar is looking very good at this moment.
