Hacker News new | ask | show | jobs
by manjalyc 2197 days ago
I would venture that the problem with Google's products is that they run in the browser and in spite of all the improvements in browsers these days its just not ready yet when you need the kind of quality and performance that huge meetings demand.

Also and perhaps more importantly, Google's approach is tied into its own ecosystem but anybody can join a Zoom meeting with just a link/code. Google had everything they needed but are too tied into the everything on the browser mindset and their own ecosystem to see they're shooting themselves in the foot before their horse is even out the door. At this point its too late, Zoom's aggressive pre-marketing, simplicity, and ubiquity is a real force now and everyone else is just playing catch up.

2 comments

> I would venture that the problem with Google's products is that they run in the browser and in spite of all the improvements in browsers these days its just not ready yet when you need the kind of quality and performance that huge meetings demand.

Disclaimer: I have not investigated how Zoom and other video conference apps work, but I do work with real-time video.

I don't see why the browser would be the limiting factor in performance / quality for videoconferencing.

What is the local client doing? Recording video and audio, and playing a real-time video stream. Sure, you want it to be low-latency, which involves its own bag of tricks.

But native-code libraries and/or hardware are doing all the heavy lifting (like H.264 encoding or whatever they use), the browser (and Javascript) is just the UI.

You have much more leeway if you can tune ffmpeg decoding settings manually, skip frames whenever you want, etc than if restricted to what webrtc gives you. Also Zoom is built with Qt which is pretty efficient :-)
So it seems the limitation is more the API for recording video, is this correct?
Even the Hangouts native app was a slow battery hog on anything but the absolute latest generation phone, so it's not a browser problem.