egsmith
egsmith on Hacker News
I would argue something is better than nothing. And if this gets people to start using the tool then maybe they will start to hit the cases where the loss of utility matters, and then this can be the source of inspiration to actually tough out the technical inspiration. Probably a long shot in general but it worked that way for me.
I was curious how the fashion industry deals with this problem.
I mean when is a pair of slacks a knock-off, a copied design, and an original design. I would think the clothing fashion industry would have way more experience with this.
This came up via Google:
http://www.nytimes.com/2007/09/04/business/worldbusiness/04i...
Somewhat old, but it reads just like these Apple v. whomever stories. Unfortunately it looks like they landed on the same solution as the tech industry; litigation. But now that I really think about it, what else can one do?
HP Makes the TouchSmart line which is an all-in-one computer and is not similar to an iMac so clearly they know how to do original design. So what they heck were they thinking when they released this product? Did they think no one would notice? It boggles the mind.
That's for a Core i7 Retina MacBook Pro and the 13-ish W power number includes the screen. The 6W number for Fluffy2 does not.
Still an impressive hack though.
I was thinking the same thing. They're rarely elected because they're rarely on the ballot.
Is that really the complete list of privledges? It says a child process can inherit the sandbox but not that a child process can be created. I mention it because I think the plug-in issue could be solved with child processes and sockets, or something similar.
Also, a typical program now can't access a generic thunderbolt device directly (it would be done via the file system which is a possible privilege). Thunderbolt devices are in PCI address space and this needs to be done via the kernel even now.
But it does raise a question: What about 3rd party device drivers?
All in all, I think most of these sandbox arguments underestimate developer creativity.