The flaws of macOS Containers and defaults
lapcatsoftware.com
lapcatsoftware.com
Don't agree with the final point though: > The third and final moral to the story is that SIP and sandboxing are terrible and ought to be abolished.
I don't think they're terrible. But I do think the user should be able to override somehow in all cases. macOS is becoming too much like iOS for my liking too. I like locking things down for security but I really to be able to make exceptions.
As long as things like SIP can still be turned off or much rather: if I can make specific exceptions without turning it off fully, they're a good thing in my book. But when macOS becomes as locked down as an iPhone it's no longer viable as a computing platform for me.
That's not why. I've been a Mac developer for 14 years and a Mac user for longer. I've seen the Mac platform enfeebled, dismantled, locked down before my eyes. The conclusion didn't follow from the blog post, it followed from my long-running frustration.
Mac software doesn't grow on trees. It needs people like me, who care deeply about this "niche". But people like me are a dying breed. You can have (the illusion of) a "secure" platform, but eventually you'll be left with nothing except apps ported from iOS. At that point, what's the Mac except an extremely overpriced iPad?
Where do I purport to do that? I speak for myself on my own blog, of course, and also here.
The implication here is everyone that's a Mac developer like you shares these opinions, that Mac-native software is going away due because developers are being pushed away by these minor hurdles. More likely, native software's going away because web-based technology has gotten better and better, and for most companies it's just more economical to be cross-platform with something like Electron.
No, I don't see how that's the implication.
It sounds like you do agree with me that native Mac software is going away. We can argue about what exactly is causing that, but I'm not sure how Mac developer opinions are directly relevant.
And I get that. I do see that native Mac software is getting more rare, even though more and more Macs are getting sold each year, as a percentage of total desktops/laptops sold.
That said, I don't feel like SIP and sandboxing are the main cause of that, and it hurts the platform to say so. You may feel like the platform is enfeebled, dismantled, locked down. I feel that it's growing with the times.
(Note that I'm not saying that everything is hunky-dory. Recently I've been experimenting with APFS. I wanted to boot from a self-configured Fusion drive, and had made a volume across an internal and an external disk. It doesn't work, which is fine. But it's not clear why not. No documentation is available, nor has anyone looked into this and blogged about it. I think that's a shame, and I have the feeling that this wasn't always like that.)
The title of the HN submission is editorialized and misrepresents the purpose of the blog post. Some people were puzzled by a mysterious behavior, and the blog post explained the mystery.
The last line was a throwaway comment, because I couldn't resist throwing in a dig at all this stuff. That's all it was. It's my blog, and no offense but I'm not really interested in having people tell me what or how to write on my blog.
Thanks for writing the post, it was quite informative.
I'm also worried about where it's going but I do think sandboxing is an inevitable need in this connected world with ever changing exploits. Like the above user said, especially for a web browser. I just wish I as the user could call the shots instead of Apple. Sometimes I just want to do something for good reason but I can't.
And yes more and more apps are becoming Catalyst port or Electron (which are mostly crap except for some gems like VS Code). But that's not only a Mac problem, all platforms struggle with this now.
Is it as convenient? Nope.
Is it good? Yup!
Security or convenience. You get one, but not both. The statement they are terrible and ought to be abolished is stupid and self serving. Yes, as a programmer it ads more steps - but the benefits they bring for everyone else who isn't a programmer (and of who there are a LOT more users) are significant and incredibly beneficial.
I used to chafe at the idea that software developers should have to be formally accredited like structural engineers and that software development should have more formality and rigor. But the more whining like I see in posts like this is starting to make me think some rigor and formality is is exactly what we need.