Wayland in 2021 • Hacker News Board

Re: Wayland in 2021

#21

Post by neolog » Sun, Mar 14, 2021, 8:56 AM UTC

xrd wrote: post #2

The author uses Pipewire with WebRTC in Chrome, very cool. Pipewire is showing up all over the place. I've been reading a little about it, but I finally got a comfortable setup of jackd and pulseaudio and am worried it might interfere with my stable setup. Am I being paranoid?

It's not perfect but mostly works.

Re: Wayland in 2021

#22

Post by knorker » Sun, Mar 14, 2021, 8:59 AM UTC

c-c-c-c-c wrote: post #15

Not a single screenshot

The book has no pictures?

It's sway. So that's what it looks like.

And the content is much deeper than showing off the color scheme you chose.

Re: Wayland in 2021

#23

Post by pjmlp » Sun, Mar 14, 2021, 9:16 AM UTC

c-c-c-c-c wrote: post #15

Not a single screenshot

It fits with the culture of working in VT-100 in the 21st century.

Re: Wayland in 2021

#24

Post by denysvitali » Sun, Mar 14, 2021, 9:33 AM UTC

If you are looking for an alternative status bar that works with sway, you can use my fork of yagostatus :)

https://github.com/denysvitali/yagostatus

Re: Wayland in 2021

#25

Post by diffeomorphism » Sun, Mar 14, 2021, 10:02 AM UTC

c-c-c-c-c wrote: post #15

Not a single screenshot

Of what would you possibly want a screenshot here?

It is about the under the hood plumbing so take any screenshot from the last years, copy it and write "this is what it looks like under wayland".

Re: Wayland in 2021

#26

Post by majewsky » Sun, Mar 14, 2021, 10:12 AM UTC

denysvitali wrote: post #24

If you are looking for an alternative status bar that works with sway, you can use my fork of yagostatus :) https://github.com/denysvitali/yagostatus

I'm using https://github.com/greshake/i3status-rust which also works well with Sway.

Re: Wayland in 2021

#27

Post by foobar33333 » Sun, Mar 14, 2021, 10:24 AM UTC

colordrops wrote: post #5

Is it still the case that Nvidia drivers don't work with Wayland?

Nvidia is basically dead at this point, no support for standards that have been around for years. And now they are including malware in their cards to slow down unapproved calculations.

Re: Wayland in 2021

#28

Post by foobar33333 » Sun, Mar 14, 2021, 10:25 AM UTC

xrd wrote: post #2

The author uses Pipewire with WebRTC in Chrome, very cool. Pipewire is showing up all over the place. I've been reading a little about it, but I finally got a comfortable setup of jackd and pulseaudio and am worried it might interfere with my stable setup. Am I being paranoid?

The next version of fedora uses pipewire instead of pulse audio. From all the people I have seen test it, they said it works much better than pulse.

Re: Wayland in 2021

#29

Post by ucosty » Sun, Mar 14, 2021, 10:34 AM UTC

shmerl wrote: post #7

colordrops wrote: post #5

Is it still the case that Nvidia drivers don't work with Wayland?

I don't expect them to ever work properly. Basically, if you care about good Wayland user experience and proper desktop integration, you should be using AMD or Intel GPU already. Waiting for Nvidia to fix this mess is pointless. Nvidia will be DOA as long as they refuse to upstream their driver or to support Nouveau to begin with. And they didn't show any interest for years.

Easier said than done, given it's nearly impossible to buy AMD GPUs at the moment (and has been for a while now)

Re: Wayland in 2021

#30

Post by solarkraft » Sun, Mar 14, 2021, 10:34 AM UTC

xrd wrote: post #2

The author uses Pipewire with WebRTC in Chrome, very cool. Pipewire is showing up all over the place. I've been reading a little about it, but I finally got a comfortable setup of jackd and pulseaudio and am worried it might interfere with my stable setup. Am I being paranoid?

Yes. I currently run it besides Pulse for screen sharing and there are no issues. I haven't replaced Pulse yet because it didn't work right away, but plan to try again eventually because Pipewire supports HFP, the less terrible Bluetooth headset profile.