Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wayland is not ready as a 1:1 compatible Xorg replacement just yet

gist.github.com

Post reply on HN
Print view View original

101–110 of 419 posts

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#101

Post by normaler »

A great tool for screen recording with wl-roots is

wf-recorder (https://github.com/ammen99/wf-recorder)

for example:

  wf-recorder --audio -f video_$(date +%F).mp4 --geometry $(slurp)
lets me select a region of my screen via slurp and then records my microphone and the screen area to the specified file.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#102

Post by tonyedgecombe »

rob74 wrote: post #78
jchw wrote: post #19

> 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…

As a complete outsider - ok, I'm a developer, but I haven't had the pleasure (?) of writing something that interfaces directly with Xorg yet - I have been reading for years about Wayland being the way forward and how Xorg is dragged down by a long history of dubious design decisions and features nobody needs anymore, and I was secretly wondering: if this is really the future of desktop Linux, why doesn't it gain more…

Aren't GTK and Qt the compatibility layers for most applications?

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#103

Post by Hitton »

dbrgn wrote: post #23

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...

That was just example. Because of Wayland's security model of sandboxing applications, none such tool will work. Currently afaik only way to do something similar is using /dev/uinput as does for instance ydotool, but its capabilities are vastly inferior.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#104

Post by canofbars »

michaelmrose wrote: post #86
LeonM wrote: post #46

Earlier quoted context omitted.

Holy sh... I've been battling this for YEARS now on X11. I'll try Wayland and see if it's better

If that doesn't why not get all high dpi hardware

For me I have a 60fps 4k monitor and a 1080p monitor. I want a higher refresh rate monitor for gaming but I do not want to drop down to 1440p on my main monitor so I am waiting for 4k high refresh rate monitors to become affordable. Wayland makes it possible to wait that out and doesn't break anything I do.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#105

Post by WhyNotHugo »

What a bunch of FUD!

I picked one a few of those issues at random, and they're entirely out of context and deliberately misrepresented.

For example, some Jitsi bugs are closed as "we can't fix this", and it's because the issue was a Firefox bug (hence, Jitsi devs could do nothing). Also Firefox did actually fix that. So, not only is the context wrong, the issue is actually solved.

Also, I used Jitsi and screen sharing on sway several times a week - works like a charm.

I've looked at a few examples, and they seem to most be misrepresented the same way.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#106

Post by xyzal »

ekianjo wrote: post #20
edent wrote: post #3

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 -…

> 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.

The clipboard issue was the bug that forced me to switch back to X11. I need to have a Windows VM running constantly due to some proprietary software at work, and copying/pasting text under wayland between the VM and linux almost never works as expected.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#107

Post by canofbars »

lawn wrote: post #55
izacus wrote: post #8

Earlier quoted context omitted.

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.

That's huge! It just might get me to try out Wayland again.

The only downside is anything running in xwayland (Essentially just apps on old versions of electron and wine) will pick the scale of one of your monitors and not switch when dragged across the border.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#108

Post by WhyNotHugo »

elric wrote: post #43
jchw wrote: post #19

> 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…

> 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.

Many seasoned Xorg developers work on Wayland. All the decades of lessons form Xorg _were_ carried over to Wayland.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#109

Post by [deleted] »

edflsafoiewq wrote: post #51
dbrgn wrote: post #23

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...

Is py37-autokey-for-Wayland possible?

[deleted]
Post reply on HN