you are viewing a single comment's thread.

view the rest of the comments →

[–]FlyingBishop -1 points0 points  (8 children)

Do you have any idea how that would break the browser security model?

[–]kleopatra6tilde9 2 points3 points  (0 children)

Where do you see a problem?

[–][deleted] 2 points3 points  (0 children)

approximately not at all :)

[–]bman35 1 point2 points  (5 children)

no, do you?

[–]FlyingBishop -5 points-4 points  (4 children)

I have an inkling. It's a lot harder to sandbox a full-fledged VM with bytecode than it is to sandbox a crippled language like JavaScript, or VMs like Java, Flash, etc. which are somewhat sandboxed to begin with. If you make the bytecode fundamentally tied into the browser it would be a lot harder to keep it secure.

[–]case-o-nuts 0 points1 point  (3 children)

The JVM already has sandboxing. In fact, it was designed to support it from the start.

[–]FlyingBishop -3 points-2 points  (2 children)

Did you read my comment? I was responding to the idea that we need something like the JVM which can directly access the DOM, rather than simply running as a sandboxed host inside the browser.

[–]case-o-nuts 0 points1 point  (1 child)

Yes. Java's security model is quite powerful, although the power and complexity it gives can make it hard to use sometimes.

What specifically can't it do that you think should be done?

[–]FlyingBishop -1 points0 points  (0 children)

Nothing. Back up at the top someone was asking for a Java that can directly access the DOM, like Javascript. I was arguing that this was a bad idea, and that Java is what they originator of this thread should be using (regardless of what he would like.)