pleroma.debian.social

It seems that a few people are being misinformed about the deprecation of the X11 backend, usually because they read screeds from well-known bad faith actors.

The X11 backend being deprecated mainly means that we're not going to spend time implementing new features, like dmabuf, graphics offloading, or Vulkan support. X11 support will still exist until GTK4 is EOL, which will happen once GTK *6* is released. We're talking about a 20 years horizon, at this point…

So, no: the sky is not falling. If you want to use X11, you will still be able to use GTK4 applications with it. You won't be able to use GTK5 applications, but those don't even exist yet.

Of course, somebody could show up tomorrow, and implement everything that the Wayland backend does, but for X11. We can always undeprecate things. We are not holding our breath, though…

@GTK and that's probably what you should have publicly communicated from the beginning, instead of acting like it is not a big deal.

@mks_h it's how deprecations have always worked. It's perfectly fine not to know things: people can always ask.

Of course, this does not deter people with an axe to grind against the project.

@GTK if you don't communicate, people will not be able to tell apart what's what. You have to battle misinformation, upfront when possible. And people have warned you about this too! You're lucky there are media outlets who responsibly explained the nuance for you.

You don't have to be a fortune teller to tell that many non-programmers would misinterpret the news out of context, and yet you left the context buried in a commit message. Get off the high horse.

@mks_h <--- @GTK probably has better things to do than https://xkcd.com/386/ ... It gets tiresome after so many years.
replies
0
announces
0
likes
2

@GTK Also, if there's really a X11 dev community left at that point people can implement a wrapper for basic functionality, even including accelerated graphics.
Running any Wayland compositor nested in a X11 session already gives you most of what you need - add a bit of integration and you should be fine, at least regarding features that are possible on X11.

@rmader @GTK >Running any Wayland compositor nested in a X11 session

it work only if GPU support creating native Waylnad surface - for many Nvidia <2014 gpus is not possible - there only x11 surface supported by proprietary driver.

@danil @rmader @GTK iirc Kepler- GPUs are supported by nouveau with reclocking? might be more worthwhile to use that at this point rather than nvidia

@halva @GTK @rmader I had used Kepler GPU last year last time - and nouveau there were in same state as it was in 2015 I first time tried open-drivers - it unusable - even GTK-gnome theme-apps there rendered incorrectly and can crash randomly (runnin any video game - there like half of graphic missing).

For cases where you stuck to old Nvidia gpu - just get new Ryzen with integrated AMD - it very affordable(relative cheap) - it support wayland and have same or better(vega8+) performance.

@danil @GTK @rmader oh wow

im an nvidia user myself but im lucky enough to be in the full support bracket for all my devices (maxwell-based laptop and turing-based desktop) by nvidia, kinda sucks there hasnt been much movement for nouveau on unsupported hardware

@halva @GTK @rmader 20xx and never series - we can hope for NVK - NVK actually works now on any RTX GPU - it actually crazy - it can run most of modern games with no bugs at all.
NVK is actual miracle if you compare it to nouveau.
There no CUDA support - but it may be possible - there some work going to try to load compiled kernels, and nvidia have extension that allow it.

@danil @halva @GTK @rmader not that crazy when you consider it basically just runs the proprietary driver... Sorry, firmware... in a dedicated coprocessor 😅

@halva @GTK @rmader I mean - pointing on nouveau for nvidia gpus - it does not work in reality.

there new NVK driver that may support Kepler - but it "not priority" and "community effort"

https://gitlab.freedesktop.org/mesa/mesa/-/issues/12531

@mks_h the issue is that "news" outlets monitor the issue tracker, and they link specific merge requests; we don't do communication management on the commit logs: we have a blog for that, which we used to explain what the deprecation means. This toot was in response to comments on social media from people who were misled.

Of course, it seems you are one of those people who enjoy ragging on the project whatever we do, so there's not much of a purpose in explaining things.