Live data from Hacker News

The X.Org Server Is Abandonware?

phoronix.com

91–100 of 714 posts

Re: The X.Org Server Is Abandonware?

#91
post #36

Earlier quoted context omitted.

systemd is hanging in 90% of all shutdowns on my machine. This never happened with sysvinit scripts.

There is a one-line fix for that. Change this line in /etc/systemd/system.conf : DefaultTimeoutStopSec=2s

It's not much of a fix, it is a workaround. The stuff that systemd says is broken will continue be broken.

Re: The X.Org Server Is Abandonware?

#92

'[...] but a prominent Intel open-source developer has conceded that the X.Org Server is pretty much "abandonware" with Wayland being the future.' So? A "prominent US politician" recently conceded that global warming is a hoax by the Chinese, with coal being the future. Should I be doubling over myself to dismantle my solar panels? Very weasel-wordy article if you ask me. X11 is fine.

Are you ok?

Re: The X.Org Server Is Abandonware?

#93
post #67

Sure X.org is abandonware but there are serious problems Wayland still hasn't solved that X has. 1) Wayland is really slow. I don't know if it's the compositing or what but it's unusable on lighter hardware that X ran fine on. 2) Widget toolkits handling window decoration is awful. Before the large number of toolkits just meant some controls were a little different but now basic behavior changes based on how programm…

Wayland is really slow. I don't know if it's the compositing or what but it's unusable on lighter hardware that X ran fine on. This is crazy when you think about it. I remember running an X server, Hummingbird I think it was called, on 386 and 486 machines connecting to Suns and it was fine , this was a perfectly acceptable way to work. Couple of xterms, an Emacs, xbiff for email, maybe some xeyes just for fun. Devel…

What could be the reason behind this? Asking as a noob.

Re: The X.Org Server Is Abandonware?

#94
This sounds like a bad case of Cult of Release.

X works perfectly for me, and there is nothing I would want it to do that it doesn't do now. Why should it change?

I have many programs I wrote years ago that I don't change and I use every day. Constant changes are not a measure of utility.

But again and again, you'll find users looking at repositories and deciding that something is "dead" because there isn't any recent commit, often blaming developers for not doing more free work for them. This is a toxic attitude. When we have a software that works well and solves our problems, we should celebrate it, not complain it doesn't find new problems to solve.

Re: The X.Org Server Is Abandonware?

#95

'[...] but a prominent Intel open-source developer has conceded that the X.Org Server is pretty much "abandonware" with Wayland being the future.' So? A "prominent US politician" recently conceded that global warming is a hoax by the Chinese, with coal being the future. Should I be doubling over myself to dismantle my solar panels? Very weasel-wordy article if you ask me. X11 is fine.

It's fine if you're stuck in time. No more releases, no changes, no fixes. It's great if you seek stability and don't want to upgrade anything for the rest of your life.

Re: The X.Org Server Is Abandonware?

#96
Nvidia doesn't care about proper support of Wayland, many devs don't care about proper support of Wayland, Wayland's configuration itself is very limited, for example, forced software compositing. As much as I want to switch from X.org, I simply can't due to these limitations

Re: The X.Org Server Is Abandonware?

#97
post #84
post #42

Earlier quoted context omitted.

Waylands design is even more broken and leads to common functionality being duplicated and broken all over the place. Each app has to do input handling on its own? Comeon, a 5yearold could tell you that that is a huge design flaw. There are equally problematic design flaws in X11, just less of them and in different areas. Where Wayland tries to get rendering right and botches all the rest, X11 is weird for rendering,…

There is no reason why window managers can't share functionality via libraries. In fact, some do (wlroots). X11 and its separation of graphic server and window manager encouraged code reuse by placing it in the server, but with Wayland that separation (and the extra context switches) are gone so there is less incentive to share code.

Which would be fine if we had something like COM to enable portable interfacing between libraries and certain level of separation, especially when a library plonks something breaking your runtime by messing with global resources (for example, threads and signals).

But we don't, and the libraries push other issues into your design as you often are forced to follow their specific idiosyncracies.

Re: The X.Org Server Is Abandonware?

#98
The last time I checked Wayland I still couldn't share only one monitor when I screen shared in Jitsi.

The CPU jumped to 100 when I recorded my desktop with OBS and had a terrible delay.

It's just not ready yet.

Re: The X.Org Server Is Abandonware?

#99

This sounds like a bad case of Cult of Release. X works perfectly for me, and there is nothing I would want it to do that it doesn't do now. Why should it change? I have many programs I wrote years ago that I don't change and I use every day. Constant changes are not a measure of utility. But again and again, you'll find users looking at repositories and deciding that something is "dead" because there isn't any recen…

We do need some form of signal that indicates a project has a maintainer though. It doesn’t matter that he has been inactive for 4 years (on that project), but if I submit a PR, it’s nice if there’s someone at the end of the line.

Re: The X.Org Server Is Abandonware?

#100

Earlier quoted context omitted.

Wayland is really slow. I don't know if it's the compositing or what but it's unusable on lighter hardware that X ran fine on. This is crazy when you think about it. I remember running an X server, Hummingbird I think it was called, on 386 and 486 machines connecting to Suns and it was fine , this was a perfectly acceptable way to work. Couple of xterms, an Emacs, xbiff for email, maybe some xeyes just for fun. Devel…

What could be the reason behind this? Asking as a noob.

I personally don’t know, but most likely when you are not forced to think about memory, efficiency, etc... most people just don’t. So if you aren’t actively developing on those lightweight systems your code won’t run efficiently on them.
Post reply on HN