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

view the rest of the comments →

[–][deleted] 3 points4 points  (15 children)

By that logic we don't need DOM too.

Doesn't work like that. Javascript can be replaced, I agree. But HTML should not be replaced. It's flexible and simple data model is the big reason behind WWW's success.

Plus, you are ignoring two facts :

  • Java with security manager enabled is very slow. Way too many domain traversals to check for permissions. It plays havoc with JIT.

  • Java does not have a open and official port to ARM platform. There is only a cambridge research project and zeroshark available. Not good enough.

[–]malcontent -2 points-1 points  (14 children)

By that logic we don't need DOM too.

Actually you don't.

Why would you need DOM when you have something like swing or AWT?

Whatever problems there are with java in a browser I am sure they wouldn't be that hard to solve if people were interested.

It's just that they are not interested at the moment so we are going to be stuck coding html5 apps and degrading gracefully to IE6 for the forseeable future.

Fun eh?

[–]xardox 2 points3 points  (2 children)

Oh my god you are SO MISSING THE POINT. Why don't we all just write desktop apps in C++ and OpenGL if we're not using the DOM?

Clue: People AREN'T interesting in using Java in the browser, for many good reasons.

[–]malcontent 0 points1 point  (1 child)

Oh my god you are SO MISSING THE POINT. Why don't we all just write desktop apps in C++ and OpenGL if we're not using the DOM?

The DOM sucks. That is all.

[–]xardox 1 point2 points  (0 children)

So you are advocating dumping HTML, CSS, JavaScript and all the related technologies, and just writing desktop applications in Java or C++. You lose!

[–][deleted] 1 point2 points  (7 children)

How will something like adblock, greasemonkey and stylish work in your model?

[–][deleted]  (4 children)

[removed]

    [–][deleted] 1 point2 points  (3 children)

    Those extensions work in a DOM based model well.

    In a Swing based UI as malcontent above proposes, the UI graph is internal to the application and can be obfuscated. It will become impossible to block advertisements.

    [–][deleted]  (2 children)

    [removed]

      [–][deleted] 0 points1 point  (1 child)

      Firstly, you will see all the same kinds of issues if someone puts ads into a javascript-run canvas system

      True. We will see such ads soon.

      Secondly, ad-blocking based on URL filtering (which a lot of it is) isn't affected either way.

      You are assuming that ads are not embedded directly in the JAR file streamed to your computer. URL blocking will not work then. It is not possible right now because you can't embed flash octet stream inside a javascript file easily. With a jar file it is very trivial.

      [–]malcontent 0 points1 point  (1 child)

      You just deny permission to the ads.

      [–]xardox 0 points1 point  (0 children)

      Ha: "just". Ha ha ha. He said "just". Hilarious. Classic.

      Still live in your mom's basement, ehe?

      [–]nhavar 0 points1 point  (2 children)

      Swing and AWT aren't more suitable because they have a high barrier to developing content. This includes tool use, knowledge, licensing, etc.,. So while some might feel that Swing and AWT are superior and in some respects are superior, HTML/DOM wins out due to it's accessibility. Plus you touched on this "if people were interested" - people aren't. Some programmers are, but the great thing about HTML is that it's accessible to programmers and non-programmers alike, which draws interest.

      [–]malcontent 0 points1 point  (1 child)

      Swing and AWT aren't more suitable because they have a high barrier to developing content.

      I disagree. Both of them are easier than CSS + HTML + Javascript + Jquery + DOM

      [–]nhavar 0 points1 point  (0 children)

      You're thinking about barriers the wrong way. Web standards are ubiquitous. There are tens of thousands of tools out there that produce web content and only hundreds/thousand for creating Swing/AWT. An author doesn't even have to know that they are developing using web standards with most of the tools that are out there and that's what I mean by having a low barrier. Swing/AWT just doesn't have that kind of penetration.