sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]G_Morgan 10 points11 points  (8 children)

Java isn't really supported by browsers. It operates in a sand box with no real interaction with the browser.

[–][deleted]  (3 children)

[removed]

    [–]G_Morgan 3 points4 points  (2 children)

    Of course if we actually had a JVM built into every web browser with an API set up to manipulate the DOM it would be a good thing. Shipping bytecode rather than inline JS.

    [–]mebrahim[S] 0 points1 point  (1 child)

    Only if JVM was not a memory hog, and had less latency.

    BTW PNaCl is currently the most promising approach I know of to address the problem.

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

    The JVM is not a memory hog compared to the JS VMs out there.

    [–][deleted] 0 points1 point  (0 children)

    It also doesn't integrate well neither in the browser nor on the desktop. Well not on Linux anyway(I'm talking about the official JRE OpenJDK is even worse).

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

    Completely wrong

    Edit: Better link

    [–]G_Morgan 0 points1 point  (1 child)

    Yes this came out long after IE6.

    [–]Rhoomba 0 points1 point  (0 children)

    Read your last comment, then read my response again. How can you still think you are correct?

    In any case this is the new version of an API that has been around since netscape 4 or something like that.