Re:How Not to Support Desktop GNU+Linux, Zoom Edition
by shadowgovt on Friday January 21, 2022 @09:54AM
(#30024273)
Zoom is not as big a company as people think... They're just hustling very hard relative to the sudden explosion of use of their tools.
I'd be willing to wager money that their development process involved attempting to use the correct API, finding that it either failed on a key executive's machine or the developers' own machines (possibly because of one bad driver/hardware/os configuration) but because it didn't work for single key player, they had to invent a work around with a worse solution that worked on the spanning set of architectures they needed it to work on.
Re:How Not to Support Desktop GNU+Linux, Zoom Edition
by computerfriend on Friday January 21, 2022 @10:21AM
(#30024698)
> In January 2020, Zoom had over 2,500 employees, with 1,396 in the United States and 1,136 in international locations. It is reported that 700 employees within a subsidiary work in China and develop Zoom software.
https://en.wikipedia.org/wiki/Zoom_Video_Communications#Work...
Re:How Not to Support Desktop GNU+Linux, Zoom Edition
by shadowgovt on Friday January 21, 2022 @10:32AM
(#30024878)
And Zoom is using that headcount to support 55 billion hours of videoconferencing a year. In contrast, YouTube is supporting only six times that much video watched annually with 40 times Zoom's staff.
"Small" is relative, but Zoom is punching above its weight for the size of its userbase and the load on its services.
Re:How Not to Support Desktop GNU+Linux, Zoom Edition
by pie_flavor on Friday January 21, 2022 @11:29AM
(#30025821)
Testing on the desktops you claim to support isn't a relative question, it's an absolute question. You can do it - or at least an approximation of it that covers the major facets like Xorg vs Wayland - with 25 employees, let alone 2500.
Re:How Not to Support Desktop GNU+Linux, Zoom Edition
by CameronNemo on Friday January 21, 2022 @01:19PM
(#30027661)
Even Chrome/Chromium, the web browser with the most developer attention period, has not enabled the pipewire screen sharing support by default.
chrome's (and by extension every electron app) issues stem from the fact it had not updated to use the screencasting APIs. afaik they've been updated.
abusing APIs isn't the right way to go here. and zoom is entirely at fault for it. they should have used the correct (and known) apis and worked with upstreams to get the support in place. then they could have properly pointed to upstream and said 'it won't work until these issues are fixed' and provided resources to fix them.
as a result now they are in a shit position of having a completely broken app when the APIs in question do work. I know because I've built a screencasting program on top of them to cast my desktop to chromecast.