So we have two anecdotes now I guess.
There are probably a couple of others you can find here and there.
Edit: Well, this thread also.
Try it when you want to control who is speaking and when.
Try it when you want to co-ordinate hundreds of participants and still want to track who has a question so you can hand the virtual mic / airtime to them.
Try it when you want breakout groups and to determine who is in which group, and after a set time for the groups to return to the main space.
What is good enough for 2 people facing each other, and appears to work perfectly well for a group of 5 or 6... doesn't quite scale to a company all-hands, or giving a lecture or seminar.
Tools fit a scale, and Zoom is excessive for the small and simple use-case but excels at the large and complex.
My company has been remote-only for about 1.5 weeks now and we have 4 different conferencing systems that people are using. It's interesting that everyone has their preferences, but for small meetings nobody is using Zoom as far as I've seen.
> or giving a ... seminar.
Zoom is good for large, hugely interactive, video conferencing and meeting.
I am unaffiliated, just a user who has used most of what is out there.
I haven't tried it this week, but that was the first thing I encountered when my university switched us to Zoom. I could join by browser in Firefox and see screenshare and video, but I would have had to also dial in to hear audio via phone. In chromium, I could get audio and video together. But, it is a more limited interface than the native client in terms of seeing attendee information. This week, I also tried chromium and saw severe audio quality issues. Joining the same meeting with the native client worked much better.
I understand that our university is consolidating and it apparently works for large lectures etc. For my own use, with small technical groups, we were happy with bluejeans before. It worked by Firefox using just webrtc functionality, AFAIK. What I've read is that Zoom is doing their own streaming and codecs, not using browser webrtc functions.
As an aside, I also encountered sudden SSO login problems in Zoom this week on Fedora. They seem to be defaulting to an embedded qt5-webengine browser and this was not working right at all. Editing their config zoomus.conf file to turn off the embedded SSO browser was the only way I could get logged in again.
I think I'd prefer an extension to installing their client.
I'm very confused now, because there have been multiple comments in this thread both confirming it doesn't work in Firefox, and confirming that it does.
I don't quite understand why Hangouts and Skype aren't more robust than they are. I'm sure this is indeed a hard problem, but the utility of getting it right is obvious, and these are massive companies.