"Sandboxing" third party app's may be an issue for app's such as "Final Cut Pro" and "Adobe Creative Suite". Manufacturers may work out a way around this issue, but plugin's such as "FxFactory" and "Trapcode" are currently causing kernel panics with such apps as "Final Cut Pro X" 10.0.4. I've had to uninstall all third party plugin's, leaving me with Apple's native effects, as my 12-Core Mac Pro 5,1 was shutting down during rendering since third party plugin's were denied use of system codec's/kext's. I'm beta testing a certain OS and it's been a reported issue Apple engineers are disinterested in addressing, believing third party manufacturers should handle this issue (even though Apple is mandating this new policy structure). Be warned, if you are a "Final Cut Pro" or creative, in upgrading your OS to 10.7 or 10.8 if you rely heavily on third party plugin's and effects.
Apple To Mandate Sandboxing by March 2012
Apple To Mandate Sandboxing by March 2012
The advantages are obvious: a sandboxed application cannot wreak havoc on the system, and thus, the user has far less chance of causing damage to his or her system. The gist is basically that any Mac OS X application can only access the data in its own application bundle (like on iOS), and that in order for the application to do anything beyond that, it has to receive special and explicit permission from Apple, dubbed an entitlement.
Another problem is plugins. Many applications - especially professional applications like Aperture, Photoshop, Final Cut Pro, and so on, all use plugins. In the sandboxed world, plugins are impossible, since applications can't even see them, let alone execute them. AppleScript is in a similar position.