it isn’t necessary to click an “allow” button in my demo. The applet runs perfectly fine in its vm (sandbox) without any security extension

To provide some clarification about java applets:
- If you want to download a “webstart” application you have to accept the download.
- if your application uses system resources like your webcam or mic you need to accept the “author/certificate”

I think this is more than reasonable.

Unfortunately, this also applies to all other libs the application needs
In these cases you are completely right – it is annoying if you have to accept an application execution more than once.

Therefore my applet only consist of a simple (harmless) loop to do some calculations and an ajax call to submit the result.

Update: (After some investigation)
- With the latest VM you accept only once for a webstart application.
- The Applet in my demo has a size of 54kb. In comparison a very small gwt app needs 45KB.

As “compelling” as it is to have a crap load of applets in a web application I think I’ll stick with the Google Web Toolkit…in both instances dorking with JavaScript DOM is avoided and the other benefits you can elucidate on your own.

PS It is Java based, and has Beanshell and Groovy additions, but none for Scala yet… perhaps you would like to contribute?

Co-existence of ACID RDBMS (for transactionality/data integrity) with NoSQL stores (for object/dynamic data types) makes sense for many scale-out web apps.

It makes even more sense if the ACID/SQL RDBMS can scale out like the NoSQL stores do. Most RDBMS would eventually bottlneck this architecture, unless the developer shards the database (messy).

VoltDB (http://www.voltdb.com) is a SQL RDBMS with ACID that scales this way (in beta now. Developed by Postgres & Ingres inventor, Mike Stonebraker). We’ll explore this use case with the VoltDB user community.