1,402 karma · joined April 1, 2016
Come on.
Congratulations, you've found the only opened bug report about clipboard on Sway/wlroots. It's triggered by edge cases (X11 client hanging + fcitx apparently), and most of it has been fixed already.
Are you really trying to convince people that the clipboard is broken on Wayland with this? Maybe you could start by actually trying Wayland.
The kernel has a pretty strong backwards-compatibility stance, so you'd need to wait a long time.
Nobody stops you from running an outdated and insecure distribution to use X11 (in this hypothetical future). Nobody stops you from patching X11 to support newer interfaces.
If you want to stick with X11, you can. Nobody urges you to upgrade.
You're just starting to re-invent the Wayland protocol. You need to pass input too… and more of Wayland re-invented.
>desktop environments are huge
Weston or Cage doesn't really qualify as huge.
Also, I think you underestimate the work to write a program using KMS and libinput. It's pretty easy to write a toy app, but writing a solid framework is something else.
It depends. In this particular case, the demo seems to contain a launcher which allows to start multiple apps and switch between them. A window manager sounds preferable in this case.
Also, Flutter handles all of the Wayland/X11 implementation details. In this case it's less work to just use the already-existing backend.
The ecosystem is still powered by the community. I see a lot of patches coming from hobbyists in many related projects.
[1]: https://gitlab.freedesktop.org/wayland/wayland-protocols
Kile seems to use Qt5, so should work without Xwayland.
> Will it work just as well as Kile on KDE Neon?
It should, yes. I don't use Kile though, so I haven't checked.
Not really, no. My company (SourceHut) has nothing to do with Wayland and is just sponsoring me for working on open-source software (_any_ open-source software). A few other developers are working for Collabora, which mainly focuses on Wayland for embedded use-cases. So, none of these companies have a real interest in pleasing desktop users.
Regardless, it doesn't mean that I personally don't care about my users, or that I want to fight against them. It's just that if you don't like something, you need to step up and do something about it to improve the situation, instead of just complaining.
Maintainers are scarce.
> it’s possible that […] your work makes the world a worse place
Always great to hear that…
Even if all developers were paid, they wouldn't be paid _by users_. It means the developers don't owe the users anything.
https://github.com/swaywm/sway/wiki/i3-Migration-Guide#commo...
We're almost there, the only issue is that there's no declarative way to advertise support for mailto links, webmails need to ask the user.