C[omp]ute

From: "andrew cooke" <andrew@...>

Date: Sat, 23 Dec 2006 20:02:20 -0300 (CLST)

Article - http://www.artima.com/lejava/articles/java_to_javascript.html
Download - http://code.google.com/webtoolkit/

From the article:

A key feature of the Google Web Toolkit (GWT) is that it allows developers
to write browser-hosted Web applications entirely in Java, and have GWT
translate that Java code into browser-specific JavaScript. In this
interview with Artima, Scott Blum, the Google software engineer behind
GWT's Java-to-JavaScript compiler, talks about the challenges of turning
Java source code into JavaScript.

And a comment on Javascript as a tool:

JavaScript is quite flexible and powerful. Most of its drawbacks, at least
to me, come not from what you can express in it—because you can express a
whole lot—it's just that it's all completely free-form, so to speak. The
power of JavaScript is also rope that you can very easily hang yourself
with.

That's why, when people are creating big class libraries, a lot of what
you're doing is convention-based. You have a convention for how you
construct a class, you have a convention for this or that, and there is no
programmatic enforcement of any of those conventions.

Which also describes how I feel about C++ memory management!

Andrew