Linked by hbbio on Thu 25th Aug 2011 22:14 UTC
General Development "Opa, a new opensource programming language aiming to make web development transparent has been publicly launched. Opa automatically generates client-side Javascript and handles communication and session control. The ultimate goal of this project is to allow writing distributed web applications using a single programming language to code application logics, database queries and user interfaces. Among existing applications already developed in Opa, some are worth a look. Best place to start is the project homepage which contains extensive documentation while the code of the technology is on GitHub. A programming challenge ends October 17th." This is weird. 'Opa' is the nickname my friends gave me 6 years ago. It's still used more often than my actual name...
Permalink for comment 486956
To read all comments associated with this story, please click here.
What are the benefits?
by ndrw on Fri 26th Aug 2011 04:37 UTC
Member since:

Sorry for a skeptical comment but I can't help the feeling that Opa is a yet another language designed to unify all languages and frameworks (like most of these languages and frameworks).

Perhaps it's a great new thing and in a couple of years we will be talking about it like we talk about JS, Python or Ruby. But the chances are it will fail like many of its predecessors. Sometimes less is better. Could someone briefly list what we can do with Opa and can't do with other languages?

Also, the application itself is rather narrow and doesn't add much value. What does "transparent web programming" mean and why it is better than "opaque web "programming"? Could anyone give a scenario in which that would be a "killer feature"?

I can give a couple of reasons why it is worse:
- it takes away flexibility in choosing server-side or client-side technology we use,
- it has fewer features (unless Opa wraps every possible framework and does it perfectly),
- it affects performance,
- it violates rule of separation of concerns - many developers want to keep server and client side separate - if only for security or keeping the server-side part private, perhaps even these parts are developed by different people who don't know much about the other side of the fence.

Reply Score: 3