Opa 1.0 Released
phy_si_kal 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."
So what does Opa actually do?
I'm an enterprise Java developer, and even I had to read that three times to work out what it's meant for.
Does this meant that opa can't handle a simple slashdotting?!!
...is that I'm really hungry for gyros!
Typical Slashdot summary. A bunch of links that tell you a little bit, no clear "main link" and no one clear link that does a clear job explaining what "Opa" is.
Why can't the articles start with a link to one major articles and (maybe) more links in the summary.
Opa Mongo Node Mongo!
I like what you have to say. Where do I sign?
I'm assuming you're referring to the type inferencing? That is done at compile time, not at runtime. Opa is statically typed.
Please post your identity and company publicly so we can all be warned against applying.
Start here.
Further reading.
There's a hell of a lot more to this issue than your prejudices. Anyone that claims either way is objectively better is a fool. The good programmer uses the tool that's suitable for the job.
Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
If I'm reading it correctly, your source needs to be distributed if it touches the opa compiler...?
OO languages that don't have strong-typing incur large overhead from not being able to optimize. I remember reading an article about someone who re-wrote parts of javascript to be type-strong, and was able to gain several factors of performance because the optimizer could tell the difference between a string and an int or whatever.
Strong typing is fine, just give flexible casting.