4 ms·
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
by olegp 15y ago
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/ 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.
- treenyc 15y agoCheck out http://ringojs.org http://ringojs.org
- olegp 15y agoI have. http://www.slideshare.net/olegp/ringo-js-talk http://www.slideshare.net/olegp/ringo-js-talk https://github.com/ringo/ringojs/commits/master?author=olegp https://github.com/ringo/ringojs/commits/master?author=olegp
- treenyc 15y agoThanks. 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.
- sktrdie 15y agoApeJS 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.