4 ms·

I haven't owned or operated a Windows machine in almost a decade, and have ten terminal tabs open as we speak; pretty sure my Unix cred is intact, thanks. And

I haven't owned or operated a Windows machine in almost a decade, and have ten terminal tabs open as we speak; pretty sure my Unix cred is intact, thanks. And I thought the Unix philosophy was to do one thing and do it well (Wikipedia agrees: http://en.wikipedia.org/wiki/Unix_way#McIlroy:_A_Quarter_Century_of_Unix http://en.wikipedia.org/wiki/Unix_way#McIlroy:_A_Quarter_Cen... ). Separating the thing that paints the screen from the thing that pushes pixels over the network seems in perfect keeping with this philosophy. Bash isn't network-transparent; if you want to use it over a network, you use SSH.

webreac 14y ago
Bash is network transparent: you change directory in a nfs filesystem or in a curlftpfs the same way as on a local disk. X separates the thing that paints the screen (the X server) from the things that computes (the X client). Your idea or pushing pixels means that you need a virtual screen on the machine where programs runs and you want to copy this virtual screen to your screen. Do you imagine the complexity of window management with such a setup ? Have you already launched many VNC clients at the same time ?