I really hate to mention this, but this perhaps answered an question of mine about why quality of code in Zoom is so low.
When I installed Zoom for Mac for the first time, I noticed it took a while to start up and caused beachballing. So I grabbed a sample of the process via Activity Monitor. To my utter horror, the Zoom binary is shelling out by calling system(3) on the fucking main thread.
I just verified this is the case on the latest version of Zoom for Mac. The binary zoom.us.app/Contents/Frameworks/zmLoader.bundle/Contents/MacOS/zmLoader invokes system(3) on three separate occasions in two functions: -[ZPMBSystemHelper disablePTAutoRestoreWindow] and -[ZPMBSystemHelper disableConfAutoRestoreWindow].
And looking at what the string was, it's just a fucking call to defaults(1). Now I'm not a Mac programming expert but I cannot understand why Zoom needs to change its own preference settings this way. This just screams sloppy software engineering quality. I guess this is what you get when you outsource software engineering.
I would not be surprised at all if someone reports vulnerabilities in Zoom, whether deliberate or accidental.
Aaaaaaahhhh this is just so horrible. There is specific in-process C and Objective-C API for this. Someone should look at this app. Maybe I will if I finish up what I’m doing.
I don't know about code quality, and I'm not ruling out privacy or security issues, but zoom must be doing something very right -- their rise to popularity regardless of there being plenty of free (!) alternatives has to come from somewhere.
It may be just anecdotal but their calls work flawlessly, regardless of number of participants, where other apps are just a laggy mess. So yes, their apps are just a means to an end and may be rushed and "low quality", but oh boy do they deliver.
When I installed Zoom for Mac for the first time, I noticed it took a while to start up and caused beachballing. So I grabbed a sample of the process via Activity Monitor. To my utter horror, the Zoom binary is shelling out by calling system(3) on the fucking main thread.
I just verified this is the case on the latest version of Zoom for Mac. The binary zoom.us.app/Contents/Frameworks/zmLoader.bundle/Contents/MacOS/zmLoader invokes system(3) on three separate occasions in two functions: -[ZPMBSystemHelper disablePTAutoRestoreWindow] and -[ZPMBSystemHelper disableConfAutoRestoreWindow].
And looking at what the string was, it's just a fucking call to defaults(1). Now I'm not a Mac programming expert but I cannot understand why Zoom needs to change its own preference settings this way. This just screams sloppy software engineering quality. I guess this is what you get when you outsource software engineering.
I would not be surprised at all if someone reports vulnerabilities in Zoom, whether deliberate or accidental.