51–60 of 419 posts
This is absurd. Author claims that "Wayland breaks automation software". They then use the "py37-autokey" tool as an example. Autokey uses Xorg APIs for key handling. Of course this is not going to work on Wayland since it's written for Xorg and not for Wayland. The author is probably the type of person that buys an AMD graphics card, and then complains that AMD "breaks" software that's based on CUDA...
> Wayland solves no issues I have This is a common sentiment, but it is kind of funny. Because software engineers working for companies will know the struggle of trying to justify reducing technical debt, improving security practices, etc. but fail to see why these things are useful to them personally when the tables turn. Wayland indeed “breaks a lot of shit” but it’s not an accident or done due to incompetence. Als…
> [...] reducing technical debt, improving security practices, etc Reducing technical debt by rewriting everything from scratch (almost?) never works. It's the baby and the bathwater. It's the sort of thing that seems attractive to junior developers, but more seasoned folks know that the legacy system contains years of embedded knowledge and workarounds for "real world" issues. The new, conceptually beautiful system…
I've been running GNOME Wayland full-time for somr three or four years now. It works just fine, with some small exceptions. AMA.
Any screen recording recommendations? Most I tried didn't work well (just didn't work, or broken keyboard shortcuts). I was a big fan of Kazam and Peek.
> Wayland solves no issues I have This is a common sentiment, but it is kind of funny. Because software engineers working for companies will know the struggle of trying to justify reducing technical debt, improving security practices, etc. but fail to see why these things are useful to them personally when the tables turn. Wayland indeed “breaks a lot of shit” but it’s not an accident or done due to incompetence. Als…
> [...] reducing technical debt, improving security practices, etc Reducing technical debt by rewriting everything from scratch (almost?) never works. It's the baby and the bathwater. It's the sort of thing that seems attractive to junior developers, but more seasoned folks know that the legacy system contains years of embedded knowledge and workarounds for "real world" issues. The new, conceptually beautiful system…
This is completely the opposite of my experience. I've been running Wayland on Pop OS since last year and it has been great. X11 had horrible tearing on external rotated screens - Wayland fixed that. Colour temperature changing works. Screensharing works just fine on Chrome and Firefox. I use it every day. Screen recording works with Gnome's built in recorder. I'm sure there are a few esoteric bits which don't work -…
Not to mention that mixed DPI screens work! I'm using Ubuntu 20.04 on an XPS13 and can finally have different scaling factors between the internal HiDPI screen and external normal DPI screen without awful issues.
Earlier quoted context omitted.
> Firefox Firefox is quite buggy on Wayland, you need to set up some environment flags before launching it, and there's a trove of bugs still open for it. https://bugzilla.mozilla.org/show_bug.cgi?id=635134 > I'm sure there are a few esoteric bits which don't work Like cut and paste between different kind of applications, which is an horrible user experience tbh.
Sorry, that's not my experience. I installed FF and launched it. No fiddling required. Everything works.
With the environment flag, it works pretty well.
On Gnome, plugins can cause issues. hidetopbar, for example, had an issue with Firefox when the screens are stacked vertically.
My biggest issue with Wayland is how it makes window managers a thing of the past. i3, xmonad, elightenment, ctwm, WindowMaker and dozens of others appeared only because X made it easy. Wayland makes developing window managers difficult again.
> Wayland solves no issues I have This is a common sentiment, but it is kind of funny. Because software engineers working for companies will know the struggle of trying to justify reducing technical debt, improving security practices, etc. but fail to see why these things are useful to them personally when the tables turn. Wayland indeed “breaks a lot of shit” but it’s not an accident or done due to incompetence. Als…
The author obviously hasn’t tried plugging a high dpi monitor in to a laptop if they don’t understand what’s wrong with X. Wayland solves so many of my problems and so far the only thing it breaks is screen capture in electron apps. And not even all electron apps. Discord has no problems.
This is the only actual, honest, problem that I've ever seen about X. Still, it does not seem a really fundamental problem, it must surely be solvable from within X? Do we really need a full-rewrite of X, unstable, with new bugs and less functionalities? (many of us don't use "desktop" applications and it will break screen capture tools, and other things that are dear to us like xwit, xdotool and the like). Just for that silly mixed-resolution screen problem? I have observed this problem, but to me is a minor, mostly irrelevant nuisance. Losing xwit would be a major problem.
> Wayland solves no issues I have This is a common sentiment, but it is kind of funny. Because software engineers working for companies will know the struggle of trying to justify reducing technical debt, improving security practices, etc. but fail to see why these things are useful to them personally when the tables turn. Wayland indeed “breaks a lot of shit” but it’s not an accident or done due to incompetence. Als…
> [...] reducing technical debt, improving security practices, etc Reducing technical debt by rewriting everything from scratch (almost?) never works. It's the baby and the bathwater. It's the sort of thing that seems attractive to junior developers, but more seasoned folks know that the legacy system contains years of embedded knowledge and workarounds for "real world" issues. The new, conceptually beautiful system…
I haven't followed the development at all but, Xorg is 16 years old and Wayland is 12. It seems counterintuitive that feature parity could not be attained in this time unless it's for philosophical reasons.
Edit: Thanks for pointing out that Xorg is actually much older. My argument indeed doesn't hold.