I was going to say “Wayland is still not ready, not all apps are compatible and needs more time”… so good they planned it in 2 years, I’m sure all apps will be compatible with Wayland then, or they will not be deserved to be used anymore. 🤣 hahaha, Wayland is amazing. Wayland is the way!
Is that satire? Wayland is pretty great, and there isn’t really a concept of “compatible app” as Xwayland handles that.
Obviously apps that perform X functions directly (clipboard managers, screen recorders, etc.) will need to be ported or rewritten, as it’s a brand new display manager, but that would be the case with any non-X platform.
Well I use a lot an app that isn’t compatible with Wayland, they already said they will work with that so if they take much longer I will just need to find an alternative… that I’m sure there will be one. I want to use Wayland because yeah, it’s great, and I love using it, but I can’t as the app I use daily isn’t compatible. I suppose not everyone uses the same apps… And that’s also why I said I will stop using it if they don’t start with the support to Wayland. 🙂
Check the input leap project. While I haven’t tested it myself, Wayland support got added like a year ago. You still needed to rebuild some packages, but reading the issue tracker now it seems to have gone a long way.
Unfortunately it is still not considered production ready. At this point I assume they will have it implemented and ready way before synergy though.
Project goals
…
… We will also have our eye on Wayland when the time comes.
Seems they still aren’t compatible with Wayland… that’s why I said if in 2 years none of they still don’t support Wayland… I’m sure there will be another tool (“Barrier” for example) that supports it and will be the time to move on to another software.
I am aware, but check the referenced issues. Support has been merged like a year ago and at least gnome on Wayland should work out of the box. It’s incomplete, but it should be working
Also barrier is considered abandoned at this point the previous maintainers forked it which actually is leap input.
Yeah, as mentioned earlier: that is an application that directly works with X to interact with the mouse cursor. It needs to be updated or rewritten. No alternative to that, I’m afraid.
@Swiggles commented that the Input Leap Project (a fork from Barrier from the active developers) already supports Wayland (I still need to mess with it). And Synergy (I think) uses Barrier, or it’s a Barrier fork also. So I will need to switch to Input Leap if I want to use it right now with Wayland! 🙂
The “TLDR” is sub heading is completely misleading. Cinnamon devs see they have to move, that’s the reason. “Begging to work” on Wayland is not at all what the article says. Before you downvote, read it. Nothing in that article or the link to one dev’s blog says anything even remotely like that.
It’s not actually based on the year. There have been 21 other major releases at various intervals starting with 1.0 in 2006. It just happens to be close to the current year right now.
At least the Mint devs are being realistic on the time span needed for Wayland to have a chance at working for everyone, unlike Fedora, KDE, and Gnome that are jumping the gun.
While maybe sometimes buggy, at least things run. I’m all for modernization, but if there are compatibility problems with recent software, I’m not OK with it being declared “the better, mature standard thing everybody should now use”.
Cinnamon and XFCE are outliers in that they try to be super stable, “complete” desktops, compared to GNOME and KDE that try to be bleeding edge and packed with new and changing features.
Benefits to both, but I can respect why Cinnamon and XFCE have been slow to adopt Wayland (to a fault, many would argue)
It’s still got issues even now, but back then they were big enough that you had to really want to use it, casual users would have become quickly frustrated.
It’s a very slow moving project by design for better or for worse. There also hasn’t been a ton of developer interest in the DE space in supporting it until the last few years since it would necessarily take resources away from other work, and generally X has been “good enough” until recently. I don’t have anything to back this up but I suspect that the increased accessibility of gaming on Linux as well as HRR and HDR displays entering the mainstream had a lot to do with this renewed interest.
Not wanting to switch to something that actually loses me functionality (Discord push-to-talk) or runs worse because I happened to buy the wrong graphics card 3 years ago isn’t being “against change”. Even if those things aren’t the fault of Wayland, they would make my desktop experience worse, so there’s no reason for me and a lot of other people to stop using X.
The video card thing, if talking about NVidia, really is wayland’s fault. The devs refuse to use the card and driver the way X did. I suspect it’s because they don’t like NVidia’s licensing of the driver, and they’re trying to make life a pain for NVidia users to for the business to make concessions.
This is the original developer/maintainer of Sway and Wlroots’ opinion on NVIDIA with regard to Wayland. This doesn’t seem like an unfair opinion to me. Gamescope breaks regularly due to bugs in NVIDIA’s proprietary driver; even if they know what the issue is, they can’t send patches to fix it because it’s proprietary. The best they can do is open a bug and beg them to fix it, which is what they do. If there’s an issue on Intel or AMD, they can just send patches upstream to Mesa, and I would guess they do.
Mind you, I’ve actually had a better experience on KDE Wayland than Xorg. Categorically…with the exception of Steam. While the games themselves play fine, the client is very glitchy. But it’s a small price to pay for all the other nonsense I’ve had to deal with on GNOME/KDE X11.
Maintainability is why wayland exists. The devs not putting up to nvidia’s special child complex in favor of a unified codebase really isn’t a surprise.
The discord thing can also be seen as a good thing (it’s a feature). Wayland is more secure and prevents apps like discord from spying on literally every keystroke you press. Especially if the app is discord, I don’t want it to be able to look at what I’m typing in real time
Not sure if that’ll stay much longer, either. I’m using using dual graphics with nVidia and Wayland on KDE works just fine. The only annoyance is that KDE doesn’t have very good touchpad gestures by default, but you also can’t modify them. Boo!
Nvidia has been decent on Wayland from my experience. Then again my experience has just been 5 days, but it feels snappier than X11 I kinda like the feel.
Nvidia on Wayland is usable but not much more than that. There are issues with Xwayland windows flickering and some general instabilities and glitches. But it works for the most part, and the 545 drivers supposedly fix lots of missing features and bugs for Wayland.
Yeah xwayland does has a lot of issues, with fullscreen wine games for example all you see is constantly zooming background instead of the game. But the finger gestures and the overall smoothness makes it worth it for me, even tho I play my games in a window. Hopefully 545 fixes that.
been using MX linux the past little while, it uses xfce - it’s not awful, but wayland looks more promising. might have to find a distro that I like that uses it
XFCE wants to be Wayland ready with XFCE 4.20, which should be released near the end of 2024. Cinnamon wants to have Wayland as default by 2026. So, in theory at least, XFCE should be Wayland-ready before Cinnamon.
Look up who had his birthday at 4/20 (American style, so 20th April) and we’ll see if you’re still praising the number. It’s associated with more than just drugs.
What is it associated with? For me, it’s just the time when the stoners smoke the weed, because at that time no one bothers or mind if you are high. And weed is a drug, as coffee and your PC addictions could be. Alcohol is a worse drug, so.
more than just drugs
On plural? How many more drugs it is about? XD I thought it was just weed…
Add comment