Stupid or Not: A Bubble/Jail Filesystem for Chrome Extensions

Note: The Stupid or Not posts are simply dumps of ideas that cross my mind and for which I have no time to research into, nor the resources to implement myself. Yet they pass the “3 days – rotten or not” test, so here it is:

Context

I was at a Google Chrome Extension event , and thought of how it would interact with the media that connects to your computer, and would extensions be able to access your filesystem to grab let say, pictures from a USB?
The answer is as usual, “yes and no.” Since the extensions are javascript, for security reasons extensions are sandboxed, so javascript by itself is not able to access the filesystem but it can load dll’s that can access it.

I got curious because:

1) Chrome OS does interact with the filesystem to provide all the same access to media(Eg. USBN Drive) that a regular OS provides.
2) Chrome browser extensions will potentially need to expand to interact with the user’s media.
3) So will this sandbox need to be breached or not?

Idea

A bubble (or jail-like filesystem) where a chunk of the filesystem is assigned to the extension so that it can interact with the media safely, similar to a jail

Idea for a simple jailed filesystem for applications of Google Chrome OS and Chrome Browser Extensions

Is this idea stupid or not? Feel free to comment!
.

Thanks Orlando for the explanation of current state of affairs of the javascript sandbox!

The Laws of Simplicity

With so much information to digest and internet services to consume, comes a thirst for simplification. No wonder as I walked down the usual isle at the bookstore of new techie books I craved for that tiny and simple little book, redundantly called The Laws of Simplicity.
About John Maeda, he is a professor at MIT’s Media Lab and has explored both Computer Science and Artistic Design.
Off to the point, here are some of the rules Maeda brings up (I will gradually expand on all of them):

1. Reduce: Achieve simplicty through “thoughtful” reduction. There is a fine balance between how complex a system needs to be and how simple can we make it, so the idea is to remove functionality until we reach the complex barrier. A most interesting observation is that about “shrinking” objects. Maeda points out that we are much more forgiving about the functioning of a smaller object than we are of a bigger one, we are surprised when a small object displays a lot of functionalitis and feautures and praise it if so, however, if it doesnt then it is expected, after all it is a small object. Small and fragile technology is “cute”, which makes me think that really, we pet our gadgets like we would a living thing.
After extraneous functionality has been removed, but we are still left with some complex functionality, an alternative is to hide it, so that “complexity becomes a switch that the owner can turn on or off.”
2. The one: Simplicity is about substracting the obvious and adding the meaningful.
3. Context: What lies in the periphery of simplicity is not peripheral.
4. Differences: Simplicity and complexity need each other.
5. Organize: Organization makes a system of many appear fewer.