Because some developers love greenfield projects. See https://news.ycombinator.com/item?id=36642796
> And that barely usable part is pure bullshit again — how else would it be the default protocol for plenty distros already?
A default that broke half of the programs I use. Thank you.
To be fair, lots of progress in the past two years. It went from 90% broken to 50% broken..
Believe me, they would have been more then happy to pop into existence a 100% backwards compatible change, but that is impossible.
I'm currently streaming X11 over my LAN which is something I can't do with Wayland. Give me a fucking solution instead of telling me I'm doing it wrong.
Yes, I'm tired of seeing all this bullshit, too. I'll switch immediately when Wayland gives me want I need to make me productive. Until then, I'm absolutely sick of this cocky attitude.
Waypipe is the solution.
Compare: https://access.redhat.com/documentation/eses/red_hat_enterpr....
With: https://access.redhat.com/documentation/eses/red_hat_enterpr...
Waypipe is the solution.
Compare: https://access.redhat.com/documentation/eses/red_hat_enterpr....
With: https://access.redhat.com/documentation/eses/red_hat_enterpr...
You can. It'll use XWayland. I'm assuming you are speaking about ssh -X or its friends. It's transparent for you, you don't have to configure anything for this. Yes, it's still using X for this use case, but I don't see how it is a Wayland issue. The protocol that talks with your hardware / local graphic stack does not have to be the same as the one talking on the network. The problematic thing is that it has X11 limitations like not changing the DPI of the window when moving it across screens, but that's also true on a X11 session.
I'm still using X11 but I'm close to switching to Wayland, KDE on Wayland has improved a lot recently.
"Don't feed egregious comments by replying; flag them instead." (a.k.a. please don't feed the trolls)
...we'd appreciate it.
So if X is so great, why exactly have the very developers who worked on it all switched to Wayland? Like, if they could made something you believe is good, shouldn’t you trust their expertise in this also?
> security model which you must actively break to get actual work
That’s literally how security models should work: you put tiny holes into a solid block. You can’t plug a swiss cheese’s holes after the fact.
> That Wayland is 10 years old and still barely usable
What exactly is your thought process here, what kind of process could change such an inherent protocol in a bazaar style ecosystem faster? It’s not apple who can just say “we are using this protocol from next year. If you wanna work, port your software”. Even if something is so much more superior than the status quo, it would need a huge amount of time to spread. Also the first 5 years of Wayland was very different from the last 5 - and it has definitely reached critical mass in the latter 5. A year now may easily introduce more progress than 5 at the beginning, from the cumulative effect of more contributors, more testers, etc.
And that barely usable part is pure bullshit again — how else would it be the default protocol for plenty distros already?