The Opa Framework for Javascript
opalang.org
The Opa Framework for Javascript
1–10 of 24 posts
Re: The Opa Framework for Javascript
#2Opa - Gangnam style: http://opalang.org/gangnam.style.html
Jokes aside, this seems like a serious project, and has some sort of connection to OWASP https://www.owasp.org/index.php/Opa
a secure javascript framework? write server side and client side in the same language (anyone said Meteor)? I'm going to try this.
prediction: HN front page posts about opa will exceed posts about Go in the next year.
EDIT: unfortunately, using TypeScript will not work here, seems Opa is generating JavaScript itself. Still interesting in any case.
Re: The Opa Framework for Javascript
#3Am I alone in thinking that all these javascript "frameworks" are getting out of control? Variety is the spice of life and all, but how about focusing on a single (open source) project, instead of all these fragmented one-offs?
Re: The Opa Framework for Javascript
#4Am I alone in thinking that all these javascript "frameworks" are getting out of control? Variety is the spice of life and all, but how about focusing on a single (open source) project, instead of all these fragmented one-offs?
Not alone, I asked the same question once: http://news.ycombinator.com/item?id=4177693
but since I've got to the conclusion, that the more the merrier, if DHH said "we have too many web frameworks, let's just invest in PHP / ASP.NET / Struts / JSP / JSF / Spring MVC" then we wouldn't have had Ruby on Rails.
If John Resig said "we have too many JS frameworks, let me just invest in mootools / dojo toolkit / scriptaculous" then we wouldn't have had jQuery probably (although some were created around the same time, but let's not allow facts to ruin my point")
So the answer, no you are not alone thinking this, but it doesn't matter, people will create more, and we all have to thank them for doing so.
Re: The Opa Framework for Javascript
#5Am I alone in thinking that all these javascript "frameworks" are getting out of control? Variety is the spice of life and all, but how about focusing on a single (open source) project, instead of all these fragmented one-offs?
abstracting away the client/server separation seems like a problem many people want to solve. It's debatable whether it's been solved in the best way we can solve it yet... so I don't see why people should stop trying.
What are you worried about, exactly?
Re: The Opa Framework for Javascript
#6Opa - Gangnam style: http://opalang.org/gangnam.style.html Jokes aside, this seems like a serious project, and has some sort of connection to OWASP https://www.owasp.org/index.php/Opa a secure javascript framework? write server side and client side in the same language (anyone said Meteor)? I'm going to try this. prediction: HN front page posts about opa will exceed posts about Go in the next year. EDIT: unfortunatel…
hahah - work time well spent
Re: The Opa Framework for Javascript
#7Exactly what we need. Another language to compile into JS. This isn't a framework. That at least might be mildly amusing.
Re: The Opa Framework for Javascript
#8Am I alone in thinking that all these javascript "frameworks" are getting out of control? Variety is the spice of life and all, but how about focusing on a single (open source) project, instead of all these fragmented one-offs?
Not alone, I asked the same question once: http://news.ycombinator.com/item?id=4177693 but since I've got to the conclusion, that the more the merrier, if DHH said "we have too many web frameworks, let's just invest in PHP / ASP.NET / Struts / JSP / JSF / Spring MVC" then we wouldn't have had Ruby on Rails. If John Resig said "we have too many JS frameworks, let me just invest in mootools / dojo toolkit / scriptaculo…
Great point of view...
Re: The Opa Framework for Javascript
#9Am I alone in thinking that all these javascript "frameworks" are getting out of control? Variety is the spice of life and all, but how about focusing on a single (open source) project, instead of all these fragmented one-offs?
Like in the past, hopefully browser authors and working groups take what is being done in JavaScript frameworks, and makes those tasks easier to implement and platform/browser agnostic.
It is work like this that is the direct reason that web developers today are able to fantastic things in CSS instead of retarded amounts of JavaScript animation and UI programming.
I doubt many of today's developers truly appreciate how amazingly easy it is do stuff like this now:
A:hover {color:orange}Re: The Opa Framework for Javascript
#10Opa - Gangnam style: http://opalang.org/gangnam.style.html Jokes aside, this seems like a serious project, and has some sort of connection to OWASP https://www.owasp.org/index.php/Opa a secure javascript framework? write server side and client side in the same language (anyone said Meteor)? I'm going to try this. prediction: HN front page posts about opa will exceed posts about Go in the next year. EDIT: unfortunatel…
I'd maybe argue that "framework" is a bit of a misnomer - Opa is a programming language based on ML (it was originally called MLState) where the compiler determines/enforces what runs on the client or server. It originally compiled down to native code on the server via OCaml as well as front-end Javascript, until the more recent switch to using Node.js on the backend. A lot of the security benefits it offers likely come from the type system (with type inference), probably similar to building a site in Haskell (compile-time errors on unclean strings, type-safe URLs, etc.).
Along side of this, it includes a slew of libraries and tools for doing things like authentication, interfacing with specific web services, and building websites, which is why it seems they've started to focus on the "framework" aspect.