Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Private APIs are understandable. It takes a while from when you make an API to when you can figure out the right kind of security model for that API. I just think that there should be a roadmap for those private APIs to become public, with some exception.

I'd say the reason why sandboxing on the Mac isn't as compelling is for a few reasons. One of them might be if you haven't personally experienced a ransomware attack. The other factor is that the sandbox is being added after-the-fact to an existing system, and it's completely opaque.



Agree with this. I'm not saying Private APIs are necessarily bad (they can be a testing ground), but after 12 years, we still don't have a solution to the "default app" issue.


I'm pretty happy with the default app situation on windows tbh - sure a fresh install is loaded with edge and warns you about switching off of it... but once you do you can forget it even exists - ditto with pretty much everything else.


The Mac does have a sandboxing mechanism which is used even without an App Store.

I like that I can write anything I want for my Mac and mostly anything I want for my phone, but I realize most people don't use their machines that way.


In what sense is the sandbox opaque? IIRC you can write your own sandbox rules in Scheme to define exactly how you want the sandbox to work.


The sandbox is opaque because the user interface does not make my expectations clear. I am not complaining about the API, I am complaining about the user experience.


Sandboxing is poorly documented, especially the parts where you can customize the list of rules you’d like your application to use.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: