Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 10 submissions in the queue.
posted by Fnord666 on Saturday February 10 2018, @08:12AM   Printer-friendly
from the maybe-Y-will-be-better dept.

Chris Siebenmann over on his personal web page at the University of Toronto writes about X networking. He points out two main shortcomings preventing realization of the original vision of network transparancy. One is network speed and latency. The other is a too narrow scope for X's communication facilities.

X's network transparency was not designed as 'it will run xterm well'; originally it was to be something that should let you run almost everything remotely, providing a full environment. Even apart from the practical issues covered in Daniel Stone's slide presentation [warning for PDF], it's clear that it's been years since X could deliver a real first class environment over the network. You cannot operate with X over the network in the same way that you do locally. Trying to do so is painful and involves many things that either don't work at all or perform so badly that you don't want to use them.

Remote display protocols remain useful, but it's time to admit another way will have to be found. What's the latest word on Wayland or Mir?

Source : X's network transparency has wound up mostly being a failure


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Insightful) by canopic jug on Saturday February 10 2018, @05:55PM (1 child)

    by canopic jug (3949) Subscriber Badge on Saturday February 10 2018, @05:55PM (#636076) Journal

    In the end they may destroy F/OSS entirely just because they can, they have money, and people will let them. I despair sometimes...

    Because they can. That's been the M$ modus operandi for decades and it still is how they work. Each and every time they have ever gotten in a position to harm other projects or businesses, they go full out to do so, even if it puts them at a disadvantage for doing so. They prefer to kill the other businesses and projects when the chance arises and they can. They have always done so enitrely just because they can. Examples are buried in some of the court records published on Groklaw's archive which contains all kinds of stuff including EEE [groklaw.net]. However, in regular news archives there are plenty of examples dead business partners that somehow thought they would be the first company ever to survive a partnership with M$.

    The part about people letting them do so is IMHO the real problem. Canonical, for example, could have gone far if they had not gone out of their way to alienate the FOSS community by allowing M$ entryism via Mono and co. That was followed up by bringing in loads of "former" M$ staff to stock key positions. Then came systemd ...

    If you despair only sometimes then, relatively speaking, you are quite the optimist.

    --
    Money is not free speech. Elections should not be auctions.
    Starting Score:    1  point
    Moderation   +2  
       Insightful=2, Total=2
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 0) by Anonymous Coward on Thursday February 15 2018, @01:29AM

    by Anonymous Coward on Thursday February 15 2018, @01:29AM (#637995)

    Funny you should mention Mono, because one of the big names behind mono is also the instigator of Gnome, and seems to always having harbored a lust of the Microsoft ecosystem...