Live data from Hacker News

The Opa Framework for Javascript

opalang.org

11–20 of 24 posts

Re: The Opa Framework for Javascript

#11
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!).

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.

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.

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.

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".

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.

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?

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).

General thoughts? Suggestions?

Re: The Opa Framework for Javascript

#13
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.

tl;dr: Give Opa a try. It's fun and enlightening.

Re: The Opa Framework for Javascript

#14

Exactly what we need. Another language to compile into JS. This isn't a framework. That at least might be mildly amusing.

If the web is really "the platform", there had damn well better be a ton of languages to choose from.

And yet we're still stuck with JS on the client side. Reality is hard to accept.

Re: The Opa Framework for Javascript

#16

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!). 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…

What happens when you want to build something besides a CRUD app?

Where do the tools that makers use come from?

Why can't you decide which way is the "winner" and find the "one way to rule them all" for what you have in mind?

Does something need to be mainstream for it to be useful?

Is it possible to both find a technology that is main stream but still at the forefront of development?

Why are you interested in JS/Node if Ruby and Python are "great" already and do what you want?

Just some questions that come to mind while reading your comment.

Re: The Opa Framework for Javascript

#17
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 ( http://www.webtoolkit.eu/jwt ) usable with any JVM language (ie including Jruby, Groovy, Jython...).

It has the advantage (compared to Opa) that you can use any database you want.

See http://www.webtoolkit.eu , really worth a try!

Re: The Opa Framework for Javascript

#19

Opa - 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…

To your prediction: Nope, Opa is an old thing already. Maybe it was a interesting project when they compiled to native code, but now it's just another way to use node.js.

I would have used it 2 years ago but there seemed to be no easy way to use HTML5 with it. It was fix with XHTML 1.1.

Re: The Opa Framework for Javascript

#20

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 ( http://www.webtoolkit.eu/jwt ) usable with any JVM language (ie including Jruby, Groovy, Jython...). It has the advantage (compared to Opa) that you can use any database you want. See http://www.webtoolkit.eu , really worth a try!

I wonder how Google indexes pages generated by Wt ... I can't really find any indexable content when looking at the examples HTML source code.
Post reply on HN