From mboxrd@z Thu Jan 1 00:00:00 1970 From: jon@fourwinds.com (Jon Steinhart) Date: Tue, 12 Sep 2017 20:01:13 -0700 Subject: [TUHS] X and NeWS history (long) In-Reply-To: <45369b52-ca6a-e9c8-06cd-79122d044dee@tnetconsulting.net> References: <201709111649.v8BGnGTx005812@darkstar.fourwinds.com> <20170911230910.GH7819@mcvoy.com> <201709120738.v8C7ckOF007026@freefriends.org> <201709121535.v8CFZOuB015695@darkstar.fourwinds.com> <201709122211.v8CMB3pf029787@darkstar.fourwinds.com> <6C032165-08F5-47CA-A30A-AD95E69996FE@bitblocks.com> <201709130056.v8D0uCix029857@darkstar.fourwinds.com> <45369b52-ca6a-e9c8-06cd-79122d044dee@tnetconsulting.net> Message-ID: <201709130301.v8D31DMZ021305@darkstar.fourwinds.com> Grant Taylor writes: > I personally really like the ability to SSH to a machine (*) using -XY > and run Oracle's installer such that it's display shows up on my notebook. Well, I agree that this is one area in which X does OK. Although, being a command line sort of guy, I'm happy to ssh into a machine and run commands. I try to avoid non-scriptable GUIs. I don't administer headless machines, and stay very far away from Oracle. I'm not sure what their installer does, but usually running X requires an installed and running system. So since a number of people have justified networked graphics we're back to the question of what an API should look like. At a very high level, it needs to be modular because there is no one thing that gets done with graphics, and there's no reason to carry a huge API around just because you need a small part of it. In particular, there is a distinction between applications that spit out geometry and those that spit out mass quantities of pixel/voxel data. Also, because of the way that this discussion started, I'm not sure whether or not resource management (windows, keyboard, etc.) falls under the umbrella of graphics. Jon