ApeJS, a tiny server-side JavaScript framework for App Engine | Hacker News Reader

ApeJS, a tiny server-side JavaScript framework for App Engine

lmatteis.github.com

47 pointssktrdie13 comments

Looks nice. What would make it even more awesome would be if you built your web framework on top of the CommonJS JSGI spec. That would allow it to run on other platforms like Common Node (http://olegp.github.com/common-node/) & by extension Node.js (without the data store part of course). This should be fairly straightforward to do and will not require that you support other CommonJS specs.

Btw, your statement "ApeJS is not compliant with CommonJS simply because all the stuff that CommonJS comes with will not work on Google App Engine where no I/O operations" is open to misinterpretation. You are able to do I/O on AppEngine by making HTTP requests to third party servers and accepting them from browsers.

ApeJS will probably only concentrate on App Engine since there are other frameworks that already achieve the CommonJS compliance that you're talking about, like RingoJS.

ApeJS is actually more about trying to create a JavaScript layer around the App Engine API, so that you can use App Engine's services in a JavaScript sort of way... think of JS callbacks for asynch Datastore queries.

Check out http://ringojs.org

I have.

http://www.slideshare.net/olegp/ringo-js-talk

https://github.com/ringo/ringojs/commits/master?author=olegp

Thanks. That is very good slides. You should email hanns, to have this slide to be featured on the ringojs page. I just did a site in Rails, thinking of migrating it o RingoJS though.

I like it. It is quite similar to my unfinished sandro-js project (http://code.google.com/p/sandrojs/).

Kudos for having a working version with a cute documentation.

Any connection to Project Ape? http://www.ape-project.org/

Not at all. Just an unfortunate semi-match of names... hopefully it won't confuse users.

Just a nitpick: JSON doesn't have functions and implies serialization. I'd just call it a javascript object.

Sure, that's why it states that it's "as easy as writing JSON".

BUT using the ":" semicolon may induce the reader to infer that the code succeeding it is JSON.

It is implied…

and this Screen Cast on deploying it on Google App http://vimeo.com/10063607

That's a screen cast of RingoJS. For an ApeJS screen cast you can watch this: http://vimeo.com/30195942

Reply on news.ycombinator.com