Red Hat Expecting X.org to “Go into Hard Maintenance Mode Fairly Quickly”

Re:Red Hat Expecting X.org to “Go into Hard Maintenance Mode... by erik_seaberg on Friday June 28, 2019 @01:59PM (#20307071)

> We don't use networked terminals to a mainframe

The mainframe is now a rack of servers, still separated from the framebuffer by a long network connection. The decline of X has us so desperate that we're abusing web browsers as remote displays.

[ Parent | on HN ]

Re:Red Hat Expecting X.org to “Go into Hard Maintenance Mode... by cesarb on Friday June 28, 2019 @03:13PM (#20307869)

> The decline of X has us so desperate that we're abusing web browsers as remote displays.

There's a fundamental difference between a X11 remote display, and an application running within a web browser. This difference becomes obvious when the network connection drops: the X11 application will immediately freeze, since all of its code was running in the remote computer, while the application within the web browser can retain some of its functionality.

[ Parent | on HN ]

Re:Red Hat Expecting X.org to “Go into Hard Maintenance Mode... by jcranmer on Friday June 28, 2019 @02:40PM (#20307531)

Is it the decline of X11, or the fact that HTML+JS+CSS has proven to be a better model for building UI applications than X11 has?

[ Parent | on HN ]

Re:Red Hat Expecting X.org to “Go into Hard Maintenance Mode... by DonHopkins on Friday June 28, 2019 @03:20PM (#20307923)

Abusing? Web browsers are much better remote displays than X-Windows servers, by a long shot.

[ Parent | on HN ]

Re:Red Hat Expecting X.org to “Go into Hard Maintenance Mode... by the_why_of_y on Friday June 28, 2019 @03:21PM (#20307935)

Do you want that rack of servers to keylog you? That's what it would be able to do with an X11 connection.

[ Parent | on HN ]