Sorry, I am probably the one to blame with the 'ORM' keyword ;)
Turns out, I've been telling for years that I don't like them, as they add yet another layer in the technology soup.
But the duo Opa + MongoDB is way different. It's a very thin layer of technology at runtime to build web applications. And I guess neither are very easy to implement.
There may have been similar solutions at the mainframe era, but the advantages of those two is that they are built on the "modern" standards and in the end allow to build applications that run in the modern browsers.

For functional reactive programming and HTML5, there is Opa. It's a new, but easy-to-learn, language which is progressing pretty quickly.

This new language exists: It's Opa!

You should look at Opa. Opa has C-bindings when you need them, and make writing and running applications much easier.

Indeed, that's what we followed with the Opa language.
No framework, simple code: It's really the best way to write web apps.

Indeed, there already is competition in that space.
Look at Opa for instance. Or Ur/Web. But of course, Google did not want to just join and contribute to an open source project :(

It's 2011, and we're probably a decade too late for bringing heavyweight Java to the client. The future might be in languages like Dart or, for quoting the same Fatal Exception's Neil McAllister, Opa.

This is good news. In related news, the recently released Opa also provides compile-time type safety for the DB, but it goes even further by providing type safety for the whole web application.

We have many comments about the license and we listen, and we thank you for them. We listen, and will engage a discussion with our community soon to see how we could make things better. However, please note that you don't have to make your code "public domain". Of course, you retain the full copyright to your code -- what we currently ask is that you make the code of the application available to your users.

Indeed, there's no such thing as the database passwd in Opa. The database is only accessed by a single application, which logics controls the access. For instance, your application code allows to create one admin user, who can choose a passwd which is stored in the database. Then, this user has the credentials to change all things when other users don't. And of course, the database content is not covered by the AGPL license.

Opa is not a new standard. It's a new language based on existing standards.

Targeting Javascript is just a small portion of the Opa code, as you can see at the Opa repo.
Indeed, should the language you mention exist, it would be easy for Opa to target it.