The issue is that their concerns were invalid, as evidenced by their own research.That doesn't make any of their concerns less valid though. As for the researcher, it may have also been on Reddit but that's not where I saw it. I wish I could find the article now. If I do, I'll drop a link.
As the only technically literate person in my immediate family, I am the only person qualified to make a good sense decision on this matter --- I'm also the person who has to fix everyones machines every time I see them.Even then, there's still an extra step with clearly written warnings every time you want to install an app. And all of this is still only if you actively choose to use sideloading at all. Which you absolutely don't have to.
No, I'm arguing that macOS has a less secure model, by allowing side loading in the first place. I'm not arguing against it -- I do my dissertation work on my MBP, and would not be able to do what I do without the open nature of macOS. But that's my choice -- if macOS didn't have this open nature, then I'd use a linux box; I wouldn't stomp my feet for macOS to do what I want simply because I want it.So you're essentially complaining that you don't want a feature that you'll never have to use and won't impact you at all included on you phone because you don't want someone else to use it on their phone. I just don't understand how that's a valid argument to you.
Things are different with my phone --- I've chosen it in part because of its locked down security features. If the model of security was changed so that the OS was OK with loading apps from outside the app store, then that is a new attack vector that can be utilized against myself. The argument against this is always "don't side load and you won't have issues," but that's invalid. You are fundamentally changing the security model of the OS, which means that there is now a potential new way for invalid software to run whether you were trying to side-load it or not. I'm not for that.