Further, that
low-level "mechanism, not policy" architecture of X is one
of its big points of existence. An X display can look and act like
ANYTHING.
And that's the problem. For most uses, the detailed design of widgets
doesn't matter. You just want a CHECKBOX here, a TEXT field here, and a
SUBMIT button there. Good enough for Amazon, at least, which is a
non-trivial UI. Plenty of other examples too.
Actually, I'd argue that the proliferation of pixel-precise layout strategies
like CSS2/3 proves the opposite, that people want low-level control over
layout and design in an interface. Otherwise, if we wanted a purely
utilitarian way of accessing resources and services over a network, we'd
be using Gopher++. Not that I'd mind that. :)
Remote computing on a intranet is interesting, less
wasteful than big
desktops, but it hasn't exactly thrived as a model. For it to do so,
would resuscitate the idea of a "workgroup" or "departmental" server
with enough grunt to virtualise desktop apps.
I don't know where you work, but in the major hospitals I work for as a
physician, I'm connecting via Citrix to a remote server where I enter my
charting. The dummy terminal is back.
--
------------------------------------ personal:
http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems *
www.floodgap.com * ckaiser at
floodgap.com
-- Greek tailor shop: "Euripedes?" "Yes -- Eumenides?"
------------------------