Linked by Thom Holwerda on Thu 3rd Nov 2011 22:54 UTC
Permalink for comment 495863
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2006-10-06
I appreciated this link.
Again, my only advice to Thom on this article would be to include other opinions, if there are any. The link above indicates that great Mac developers like Agile (makers of the uber cool 1Password) are cool with sandboxing, even if it does mean some trade offs.
I would have appreciated more context on what sandboxing is, how many other operating systems use it, etc..
It seems to me that Apple won't disapprove of an ftp application, because accessing a remote server is within its basic functionality.
On the other hand, if I submit a JPG to PNG converter utility and it needs to access a remote server every time it starts up, probably a poorly designed program and a security risk. Is that the idea behind sandboxing? Or is it more about keeping apps within their own boundaries to minimize bugs and other issues?