Comment Re:in answer to the original questions... (Score 1) 539
Using your "logic" we might decide TCP/IP is a
total loser too. I mean what a lousy standard.
There are at least a dozen different methods
to just transfer a file -- FTP, HTTP, telnet
upload, Gopher, rdist, tar over rsh, rcp, NFS,
DFS, TFTP, ...
Just because you re-define a word (X11) to mean
something different than the designers intended
doesn't give you the wisdom to pronounce it a
failure.
X is a pretty decent standard. It definitely
needs some redesign to fix today's problems --
optimize for high speed local multi-processors
with huge memories for example. The lack of a
user interface standard is a problem that can't
be fixed by changing X. The only solution to
that problem is to prevent people from designing
new toolkits.
BTW, the commercial Unix community *has* a
standard user interface toolkit. It's called
Motif. You don't like that? You want to have
a different toolkit? Well, then don't bitch
because X has so many tookits!
total loser too. I mean what a lousy standard.
There are at least a dozen different methods
to just transfer a file -- FTP, HTTP, telnet
upload, Gopher, rdist, tar over rsh, rcp, NFS,
DFS, TFTP,
Just because you re-define a word (X11) to mean
something different than the designers intended
doesn't give you the wisdom to pronounce it a
failure.
X is a pretty decent standard. It definitely
needs some redesign to fix today's problems --
optimize for high speed local multi-processors
with huge memories for example. The lack of a
user interface standard is a problem that can't
be fixed by changing X. The only solution to
that problem is to prevent people from designing
new toolkits.
BTW, the commercial Unix community *has* a
standard user interface toolkit. It's called
Motif. You don't like that? You want to have
a different toolkit? Well, then don't bitch
because X has so many tookits!
