another interpreted language running inside of an interpreted language... sweet. All we need now is to write a perl interpreter in Lua and then run it inside of the javascript Lua interpreter and we'll really see the scripts slow down to a crawl.

It would still run about as well as Tcl. [ducks]

Lets add an Io interpreter to the mix!

(For those who don't know: Io is very powerful, but also very slow.)

Steve Dekorte (creator of Io) has already been thinking about an Io implementation on top of Javascript.

ref: http://tech.groups.yahoo.com/group/iolanguage/message/12526

Should be a relatively good fit, with both languages having prototypal oo. I wonder how he would implement the metaprogramming parts of Io.

I see its actually more than just thinking because he has a repo called "Io port to Javascript (node.js)" on github: https://github.com/stevedekorte/oia

This is nice, but the API requires your app to communicate back to some central web server in order to function...

The question is not is opentable worth it, the question is this question worth it being posted on this site, or is it just completely irrelevent drivel? I'd say the latter is true.

Excellent business opportunity is not material for HN?

Oracle's lawsuit against google was the last nail in the coffin for Java. If I were you, and was forced to using java code, I would definately either use gcj to compile directly to native object code, or use an oracle supported JVM.

welcome to iran

um yeah - what's wrong with plan ole http? curl has never come up short.

The aim of the project was to make htty an incremental advance over curl by layering aspects of a browser UX on top of it. What you get with htty that curl doesn't give you is primarily a session, and consequently a history. The other features are icing on the cake.

In the near future, the difference will be more striking. The ability to parse and build requests on various media types will make htty even better at the tasks of both API exploration and HTML screen-scraping.

definitely a cool project. Cool to experiment with UX on top of http. I guess the thing that rubbed me the wrong way initially is I really like seeing request / response. As a developer I learn alot from watching those; and anytime I have bugs in my http it's typically a header problem, so I like seeing those front and center.