Hacker News new | ask | show | jobs
by giancarlostoro 2543 days ago
I am not a big Zoom fan but everyone else but me at work has issues with Zoom. One vendor we do calls with sometimes gets the web version instead of the desktop version any time he joins a Zoom call.

My biggest pet peeve was Ciscos version. I had to install: a browser plugin, which wasnt used, then a desktop app, then a follow up desktop app to support voice and audio. What the actual heck is Cisco smoking!? I was shocked. I cannot believe the sheer incompetency and what saddens me is they probably advertise Webex as a solution but it is such garbage on a Mac. I dare not ask what its like on Windows or Linux (ha!). I hate to say it but Webex might benefit from becoming an Electron app.

1 comments

Webex and Zoom are absolutely not the same product, they are competitive offerings from different companies.
> My biggest pet peeve was Ciscos version.

I mentioned this, I just went off on a tangeant cause it amazes me how broken some of these pieces of software are, it's a problem we solved a long time ago (audio and video conferencing) and it seems only Electron based apps have been getting it right lately for whatever reason.

If Zoom has a web-based client, I haven't seen it. I know that WebEx has a web-only client. I thought you had them like, really confused, y'know?

Turns out there is a Zoom Web Client though and I'm all wet.

All good, but yeah, I didn't know either, sounds like it is yet another one of those "works best in Chrome" clients, I usually use Firefox, and it probably tries to open Zoom. Maybe sometimes people click "open in browser" instead or something? Not sure...

What's worse is WebEx is supposed to be web only supposedly, but I installed 3 things to use it... Totally not HTML5 friendly at all...

For anybody interested in the Zoom web client:

https://support.zoom.us/hc/en-us/articles/214629443

Their web client is actually doing something quite interesting. Instead of using webRTC, they load a webassembly video codec. They then encode frames in a webworker and transport them via websockets over their servers.