Live data from Hacker News

How Not to Support Desktop GNU+Linux, Zoom Edition

write.as

221–223 of 223 posts

Re: How Not to Support Desktop GNU+Linux, Zoom Edition

#221

Earlier quoted context omitted.

Debian has switched to Wayland with the release of buster (version 10) in 2019. https://www.debian.org/releases/buster/amd64/release-notes/c...

The Debian default became Wayland with Buster. Xorg is still supported. The very second sentence of the linked release notes states that Xorg is still installed by default.

Yes, of course. Same as every other distro that defaults to Wayland today.

Re: How Not to Support Desktop GNU+Linux, Zoom Edition

#222

a few comments from somebody who worked for many years for a competitor to Zoom. The article author complains about some relatively minor details but completely misses the big picture. I'm not going to talk about the availability and quality of the Wayland API, this was covered in other posts. Here is what the decision looks like from the POV of someone building a product: - Zoom is one of the few collaboration produ…

> The native clients offer much better performance on every operating system. Background blur uses significantly less CPU in Google Meet running as a chrome/chromium tab, than in native Zoom Linux client. Besides, Zoom Linux client also makes some arbitrary decision that my more powerful i7-3720QM is not qualified to have background blur enabled, while my less powerful i5-8250U is allowed to do so. Background blur wo…

My comments are directed at the general performance of Video and Audio components. Zoom implements their own protocol which performs better than the WebRTC. Their codecs are also better optimized, on of the reasons being that VP8 lacks hardware optimization on many platforms.

Background blur most likely require GPU optimization. The implementation on Windows/Mac and Linux looked different for a while. It is possible that they had to deal with compatibility and driver issues on Linux.

Re: How Not to Support Desktop GNU+Linux, Zoom Edition

#223

Earlier quoted context omitted.

Has anyone tried using an AMD card for desktop/Wayland alongside an Nvidia card for ML/CUDA? Especially with Sway? I use Sway/AMD for desktop but all the photogrammetry software out there requires CUDA. It's a bit of a PITA.

It can work but generally you either have performance issues or less library support or run into more operational pains. I mainly work on building library tooling over tensorflow. Losing support for good number of operations is not something that I could reasonably consider. Also cloud amd gpu support is near non-existent and most of my company's compute relies on the cloud. t4 pricing is very nice on gcp. Like AMD r…

Sorry, I think you misunderstood. This is installing both types of card in the same computer: one for desktop/Wayland (AMD), and the other for ML/CUDA (Nvidia).
Post reply on HN