X11 is in the news again, so I thought it would make sense to be clear about the Plasma team’s plans for X11 support going forward. Current status: Plasma’s X11 session continues to be …
Why still use WordPress when KDE has its own blog?
Can you guys make a blog account to one of the most known KDE people that he can write his personal opinions there? This post really should be on kde.org.
Gonna be down voted to oblivion, but doesn’t matter, here goes:
Rgarding x11, this is a shame that it hasn’t been dropped already. Investing time and effort into a sad story instead of investing into improving Wayland session and apps. This kind of behavior is known in the corporate environment as sunk costs.
It’s a shame that KDE is always a follower given a huge advantage in Qt toolkit.
A lot of KDE dev and community post their stuff (like future planning, technical stuff, experience sharing) on their own blog, then later get listed on KDE Planet (https://planet.kde.org/)
I’m not sure how much actual effort it takes to make sure Plasma keeps compiling for X11, but based on the wording from the blog post it sounds like they’re exerting pretty much as little effort as possible. I would say with the recent uptick in leading-edge distros moving to Wayland it’s only a matter of time before almost no one is left on X11, which will deprioritize it even further. Pulling the plug on X11 today is premature given how many people are still running it (SteamOS uses it by default, for example), but I think their ~2 year estimate sounds about right for letting off the gas and putting a hard stop on support.
Any effort in this area is too much since it is for sure wasted. Even Bugfixes.
If people want to use it, they should have stuck with plasma lts or use an lts distro.
I know I’m not majority with this opinion, but plasma 6 should have dropped x11. Plasma 7 should drop xwayland.
Not only does this make sense effort wise, but it prioritizes future and not past development.
Valve can stay with older kwin version and/or support move to Wayland with SDL improvements and whatever else is needed. Not that they lack resources… Also Vulkan.
Why still use WordPress when KDE has its own blog?
Can you guys make a blog account to one of the most known KDE people that he can write his personal opinions there? This post really should be on kde.org.
Gonna be down voted to oblivion, but doesn’t matter, here goes:
Rgarding x11, this is a shame that it hasn’t been dropped already. Investing time and effort into a sad story instead of investing into improving Wayland session and apps. This kind of behavior is known in the corporate environment as sunk costs.
It’s a shame that KDE is always a follower given a huge advantage in Qt toolkit.
A lot of KDE dev and community post their stuff (like future planning, technical stuff, experience sharing) on their own blog, then later get listed on KDE Planet (https://planet.kde.org/)
I’m not sure how much actual effort it takes to make sure Plasma keeps compiling for X11, but based on the wording from the blog post it sounds like they’re exerting pretty much as little effort as possible. I would say with the recent uptick in leading-edge distros moving to Wayland it’s only a matter of time before almost no one is left on X11, which will deprioritize it even further. Pulling the plug on X11 today is premature given how many people are still running it (SteamOS uses it by default, for example), but I think their ~2 year estimate sounds about right for letting off the gas and putting a hard stop on support.
Any effort in this area is too much since it is for sure wasted. Even Bugfixes. If people want to use it, they should have stuck with plasma lts or use an lts distro.
I know I’m not majority with this opinion, but plasma 6 should have dropped x11. Plasma 7 should drop xwayland.
Not only does this make sense effort wise, but it prioritizes future and not past development.
Valve can stay with older kwin version and/or support move to Wayland with SDL improvements and whatever else is needed. Not that they lack resources… Also Vulkan.