Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


+ - Opa JS Framework Hits Major Milestone->

Submitted by phy_si_kal
phy_si_kal (729421) writes "The Opa Framework allows to build JavaScript applications that run on NodeJS and MongoDB.
Since its 1.0 release, the Opa framework has switched to a more liberal MIT License and was a finalist of GigaOM's Structure 2012.
The project hit today a major milestone, releasing a version which is 38% smaller, generates 62% smaller apps, that run 49% faster while using 29% less memory.
That's good news before the Opa Developer Challenge ends."

Link to Original Source

+ - Opa 1.0 Released->

Submitted by phy_si_kal
phy_si_kal (729421) writes "The open source Opa project just released its 1.0 version. Opa appeared last year and was discussed a few times.

Throughout the year, Opa adopted a JavaScript-like syntax, gained support for MongoDB and now Node.js.
Opa positions itself as the enterprise JavaScript framework due to the safety and security provided by its strong static typing system.

Indeed, Opa checks the type safety of the application over the whole application, from client, to server, to database. Opa also provides many automation algorithms, such as the automated use of Node.js fibers at runtime, automated client/server and server/database dialog.

The site of the project also announces a developer challenge."

Link to Original Source

Comment: Re:Just because you have a hammer.. (Score 1) 29

by phy_si_kal (#39127509) Attached to: New Opa S4 Release Puts Forward New 'ORM' For MongoDB
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.

+ - New Opa S4 release puts forward new "ORM" for MongoDB->

Submitted by phy_si_kal
phy_si_kal (729421) writes "The new, open source, Opa web programming language just hit version 0.9.0 "S4", six month after its last major release.
Apart from a new syntax more similar to JavaScript, the new releases focuses on mongoDB integration.
Opa now features something similar to ORM except that mongoDB is a non-relational, document-oriented database and Opa a functional, non-object-oriented language.
The new functionality makes the NoSQL database even easier to use as all language-database calls are automated. And the mapping of functional datastructures to documents could even be much better than current ORM approaches and solve the object-relational impedance mismatch."

Link to Original Source

Comment: Re:Wt (Score 1) 253

by phy_si_kal (#37241796) Attached to: Announcing Opa: Making Web Programming Transparent
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.

Comment: Re:Which open-source license? (Score 1) 253

by phy_si_kal (#37233088) Attached to: Announcing Opa: Making Web Programming Transparent
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.

... though his invention worked superbly -- his theory was a crock of sewage from beginning to end. -- Vernor Vinge, "The Peace War"