Opa - Gangnam style: <a href="http://opalang.org/gangnam.style.html" rel="nofollow">http://opalang.org/gangnam.style.html</a><p>Jokes aside, this seems like a serious project, and has some sort of connection to OWASP <a href="https://www.owasp.org/index.php/Opa" rel="nofollow">https://www.owasp.org/index.php/Opa</a><p>a secure javascript framework? write server side and client side in the same language (anyone said Meteor)? I'm going to try this.<p>prediction: HN front page posts about opa will exceed posts about Go in the next year.<p>EDIT: unfortunately, using TypeScript will not work here, seems Opa is generating JavaScript itself. Still interesting in any case.
Apologies if this comes across as as a bit off topic at first, but I typically think of 2 types of software developers: tinkerers and makers (this is simplistic thinking, I know, but go with me here...nothing derogatory is meant!).<p>Tinkerers like to fiddle, muck around and generally like the internals. They do make awesome stuff, though they like the tools just as much as they like the end product. Errors on install or obscure messages are just another reason to dive deep.<p>Makers are people that like to make things; products and such. They tend to care less about the tools and more about the product they are working on. Errors on install or obscure messages are hurdles that get in the way of building the products.<p>I'm a maker. Right now I feel the current state of Node and JS is not a great place for makers. Ruby and Python (as examples) are great.<p>I would like to use Node and JS, though I feel that there is just too much choice right now with no real "winner" and no clear "one way to rule them all".<p>Perhaps I'm wrong, and I would love to get educated on this b/c reading the tea leaves would suggest that JS/Node can be huge in about 3-5 years, maybe even mainstream. And as a person who likes to be at the forefront of technology, I would love to spend some time with JS/Node right now...but it just seems crazy. As I said, so much choice, no clear direction, too many ways of doing things.<p>So, the question would be this: if someone like me wants to get started, where do I start? Which web framework should I be using? Coffescript? Deployment?<p>I've seen Meteor and am intrigued (the fact that the setup instructions don't work on Ubuntu is a HUGE minus, btw...gah! another hurdle).<p>General thoughts? Suggestions?
Wt is also a framework enabling you to develop web applications without the need to manage client-server communications. It's available as a C++ version and a java version ( <a href="http://www.webtoolkit.eu/jwt" rel="nofollow">http://www.webtoolkit.eu/jwt</a> ) usable with any JVM language (ie including Jruby, Groovy, Jython...).<p>It has the advantage (compared to Opa) that you can use any database you want.<p>See <a href="http://www.webtoolkit.eu" rel="nofollow">http://www.webtoolkit.eu</a> , really worth a try!
I've used Opa sporadically since before the new JS syntax/backend. It's just flat out fun to program with, as the feedback loop is so tight. The only complaint I had was the compiler was a bit ... French -- liable to take an extended lunch break just when you ask it to do some work. It might be faster now. Use a structural type system gives the language a very different feel to other statically typed systems.<p>tl;dr: Give Opa a try. It's fun and enlightening.
Am 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?
This definitely needs to be your theme song: <a href="https://www.youtube.com/watch?v=-lnh3h3-lyQ" rel="nofollow">https://www.youtube.com/watch?v=-lnh3h3-lyQ</a>