Linked by Kroc Camen on Thu 1st Oct 2009 21:02 UTC
Thread beginning with comment 387372
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
What use is a network transparent design that doesn't get used? Even on Linux today most people use VNC, RDP, Citrix to access remote resources because they don't really require any special command line options to get them to work.
I don't know anyone who uses X over ssh anymore. I've tried it myself a few times, but I get better performance if I just choose to use a full remote desktop like VNC or NX. Especially NX just is so much faster. Not to mention the fact that I don't lose what I was doing if the network goes down or anything like that.
I don't know anyone who uses X over ssh anymore. I've tried it myself a few times, but I get better performance if I just choose to use a full remote desktop like VNC or NX. Especially NX just is so much faster. Not to mention the fact that I don't lose what I was doing if the network goes down or anything like that.
VNC sucks, big time. It's a hack for Windows. Anyone who use it on linux is clueless. It's far slower than X and you can do much less.
I know a lot of people who use X over ssh. That is the way we administer servers in my job. They have linux servers and windows clients. Xming is installed on each window client. X forwarding is providing a clean integration in the windows desktop, unlike VNC, which sucks (big time).
BTW, RDP sucks and so does Citrix. And Citrix costs an arm and a leg and is a pain. freeNX is the way to go if you have slow network. If network is faster than you need, then X over ssh is perfect. Just don't use VNC if you can avoid it, it sucks!
Edited 2009-10-02 15:21 UTC
What use is a network transparent design that doesn't get used?
Using it every day, I find this quite funny.
There are real issues with X, performance is one of the top complaints against it.
Which performance?
-Remote display performance? Agreed (It should really include NX style compression natively).
-Local display performance? I disagree: I find it good enough (the responsiveness issue I feel are caused by applications such as Firefox which have a poor design and are the same on Windows).
Using both Windows and Linux, I don't understand why you find performance of X such a big issue..
X itself is the least forward thinking part of Linux.
Given that it had network transparence far before the competition, I find this quite laughable.
As for the rest, yes, stripping the drivers out of X is a good idea, and more competition is always good.
I wish Wayland the best but don't forget that there are already many dead X competitors: Berlin/Fresco, Y, etc.






Member since:
2007-02-17
What use is a network transparent design that doesn't get used? Even on Linux today most people use VNC, RDP, Citrix to access remote resources because they don't really require any special command line options to get them to work. There are real issues with X, performance is one of the top complaints against it. The real problem with X is that it wasn;t designed with real desktop use in mind, instead its getting retrofitted for that purpose and it shows. IMO, it probably would have been easier to start something new and there have been plenty of opportunities for this to happen but we keep chinking away at the same old codebase in hopes of making it work properly. Why, because of compatibility which is something we constantly berate MS for doing with windows. X is no different. X itself is the least forward thinking part of Linux.
Like I said before, once the drivers are removed from X and put in the kernel where they belong then it would be much easier to replace X altogether if that is what the community chooses to do (and I hope they do). There are alternatives in the sideline waiting to take its place. Wayland is a great candidate, imo.