Recent searches
Search options
Administered by:
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…
@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 How did they not make it clear in the blog post that announced it?
What do you think should they do different?
@mks_h @GTK The post in the GTK Development Blog stated,
"The X11 and Broadway backends have been deprecated, as a clear signal that we intend to remove them in the GTK 5. In the meantime, they continue to be available"
It is a reasonable assumption that people reading the development blog have a rough understanding of the major gtk release cycle(aka ~10 years) with gtk4 in 2020
It could probably have been made clearer, but that blog probably wasn't the place to describe the gtk release cycle
@mks_h Let's be honest: if there were the most detailed information, people would still share false information from some clickbait they saw in a thumbnail or from some random blog.
People won't want to listen because they're already willing to find any tiny detail to justify the hate.
@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.
@GTK I actually don't enjoy doing that. Sorry, I guess I was too harsh in my comment. You did kind of communicate it, and of course you'd still receive enough misinformation from some bad actors whatever you did. I just wish you'd take this more seriously, and reassure people upfront. This would not eliminate misinformation, but it would make it more obvious and less effective. But I guess this isn't that big of a deal in the end. Again, sorry for being too harsh.