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.
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.
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.
My fault. The word transparent comes from the original article, but not from opalang site.
As for cloud, it clearly lacks a meaning;) I take it as distributed+easy to deploy, so Opa will be the cloud language once it can automatically deploy apps on EC2, Rackspace, etc.
You don't use Google?
You don't use Twitter?
You don't use Facebook?
Honestly, the web is evolving towards applications. And the truth behind applications is that they need to run some code on the client side. You may not like it, but with or without this new technology, there will be probably few sites which will work without JS code running on the client in a few years.
You're the debian packager for Wt, so you must know Wt much better than I do.
However, both projects are very different and you should probably have a real look at Opa before popping up on every story about Opa (followed by another comment by someone else saying the link was useful, history repeats;).
Opa is high-level language for writing web apps.
Wt is a toolkit for writing web components in C++.
There is an order of magnitude between the length of application code in Opa and in Wt. Wt handles everything as strings and does not perform any verification on the soundness of the application -- it's a way simpler project.
But on the other hand it is useful to add a web touch to existing C++ desktop apps.
Opa is a recently released open source technology that mixes together front-end and back-end code.
See http://opalang.org/
Also, there are packages for MacOSX, which is probably your environment;)
If you can try it, I'm really curious about how easy it is for a non-programmer to learn this kind of programming language.
This seems quite strange, if we consider that AdWords was the first miracle for Google's business in 2000.
Do people really want to see video ads? Isn't it even more disturbing than banners? I hate the flash video ads in imdb for example. In the beginning, they even had sound turned on by default!
Google isn't completely stupid, since they won't try this on their own site... Maybe only a move to suggest bad ideas to its competitors;)
When I had my 486SX-25, it was fast enough for me. I could launch every app quickly, everything was responsive. Programming with Borland Pascal 7 was a pleasure compared to my previous computer...
But time goes by... and even if my "old" Northwood 1.6A is now enough, someday, I'll change and won't get back.
I confess though that programming with old hardware leads to good programming practices and makes me write more optimized code.
Slashdot Mirror
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.
My fault. The word transparent comes from the original article, but not from opalang site. As for cloud, it clearly lacks a meaning ;) I take it as distributed+easy to deploy, so Opa will be the cloud language once it can automatically deploy apps on EC2, Rackspace, etc.
You don't use Google? You don't use Twitter? You don't use Facebook? Honestly, the web is evolving towards applications. And the truth behind applications is that they need to run some code on the client side. You may not like it, but with or without this new technology, there will be probably few sites which will work without JS code running on the client in a few years.
You're the debian packager for Wt, so you must know Wt much better than I do. However, both projects are very different and you should probably have a real look at Opa before popping up on every story about Opa (followed by another comment by someone else saying the link was useful, history repeats ;).
Opa is high-level language for writing web apps.
Wt is a toolkit for writing web components in C++.
There is an order of magnitude between the length of application code in Opa and in Wt. Wt handles everything as strings and does not perform any verification on the soundness of the application -- it's a way simpler project.
But on the other hand it is useful to add a web touch to existing C++ desktop apps.
And this one: http://opalang.org/sdfdsfafdsfsdofndsf
After all, the site is named flashuser... so quality is not expected here ;)
Opa is only for web applications (or webservices) But indeed, it's a very good language to program them, as a concurrent alternative to Scala + Lift.
Opa is a recently released open source technology that mixes together front-end and back-end code. See http://opalang.org/ Also, there are packages for MacOSX, which is probably your environment ;)
If you can try it, I'm really curious about how easy it is for a non-programmer to learn this kind of programming language.
There has been some approaches to deal with web programming, redone. I'm thinking about OPA at http://mlstate.com/ in particular.
Would you please be ever so kind to read grand-parent and parent (aka the thread). Do you need a (gimp) picture?
I don't get your rant: Linux can't even run GUI applications, so there is really no alternative to Windows. -- Upgrade to 7 now.
Well, the Afghans have mules, that cost nearly 0 and already pass where Humvee's stop. http://www.csmonitor.com/USA/Military/2009/0504/p22s01-usmi.html
This seems quite strange, if we consider that AdWords was the first miracle for Google's business in 2000. ;)
Do people really want to see video ads? Isn't it even more disturbing than banners? I hate the flash video ads in imdb for example. In the beginning, they even had sound turned on by default!
Google isn't completely stupid, since they won't try this on their own site... Maybe only a move to suggest bad ideas to its competitors
When I had my 486SX-25, it was fast enough for me. I could launch every app quickly, everything was responsive. Programming with Borland Pascal 7 was a pleasure compared to my previous computer...
But time goes by... and even if my "old" Northwood 1.6A is now enough, someday, I'll change and won't get back. I confess though that programming with old hardware leads to good programming practices and makes me write more optimized code.