On 30 nov, 17:57, Mark Volkmann <[email protected]> wrote: > On Mon, Nov 30, 2009 at 12:31 PM, opinali <[email protected]> wrote: > > Unfortunately, JavaScript (plus its DOM interface with the outside > > world) is a pretty poor choice for such UVM role. > > Yeah, everybody complains about the DOM. I'm not suggesting coding to > that though. You really have to experience a library like jQuery to > appreciate how much better it is than coding to the DOM.
I was not talking about programming convenience (though I hate JS/DOM/ HTML and will gladly adopt GWT, jQuery (I've used it briefly), JSF or ANYTHING that shields me from the horror that is "web programming"). I was talking about performance. Any "Universal VM" must contain efficient runtime components - bytecode, core APIs, GC/threads/etc. - so higher-level languages/toolkits can target it. The DOM is a very heavyweight component. Laying sophisticated libraries like jQuery on top of it, won't make it any faster. Even high-performance components like canvas, video and WebGL (that are fast because their implementation is mostly a native binding to accelerated codecs and graphic pipelines) will suffer a lot if they must be driven by massive amounts of DOM objects and/or JavaScript code. > What I'm suggesting is coding only the user interface in JavaScript. > All other code can be in the language of your choosing and run on the > server. The user interface code can easily access it with RESTful > requests. This is fine for client-server like apps, I agree that this covers most corporative apps. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
