node-v0.x-archive

When you break up your application up as a set of tasks, which GAE pretty much requires, it's hard to execute them in any sort of order. Your program is not executing sequentially so there aren't any while loops and if-then statements to make sure calculations happen in a certain sequence. So you need a higher level kind system that can order everything. Node.js which is a similar sort of event driven system, but not distributed, has a number of similar libraries https://github.com/ry/node/wiki/modules under Flow control / Async goodies.

Looks like this Node patch includes Crankshaft: https://github.com/ry/node/commit/c30f1137121315b0d3641af6dc...

If you haven't already seen this list, make sure to check it out: https://github.com/ry/node/wiki/modules

Although I have never built a "complete website" on the node.js stack, the time that I have spent developing on the platform has been very enjoyable and I've put a decent amount of effort in. There are many articles as well as github repositories that can teach you what you need to know to get up and running. I recommend https://github.com/ry/node/wiki and http://expressjs.com/ for reading on the subject. Good Luck!

https://github.com/ry/node/wiki < there is a good list of companies using node.js in production.

I'm using tuxychandru's grasshopper which does templating (an a lot more - it's a full fledged web server) in a relatively nice way. http://github.com/tuxychandru/grasshopper Another good approach, if you're looking for something that specifically plays well with node, is to look at the modules page on the node.js wiki - it's served me well. http://github.com/ry/node/wiki/Modules

Google. http://www.google.com/search?q=node.js+web+framework&ie=... The search turns up an interesting blog: http://fleegix.org/articles/2010-03-15-geddy-web-framework-f... ...and the blog has a link to a list of exiting web frameworks (also the fourth hit in the google search): http://github.com/ry/node/wiki/modules Learn from what others have done and build on it.

not really. The problem is the way that projects are dependent on other projects. It is especially illustrative, if you use a package manager like apt-get. Installing something pulls in tons of other libraries/dependencies. When you want to build something, you would want to build against their dependencies.. which you would want to tag in some manner. For e.g. v1.0 of ProjA needs v0.8 of ProjB and v3.2 of ProjC. A nice example is NodeJS that needs The GoogleV8 engine. Take a look at the number of changesets that are simply managing revisions of V8 inside the NodeJS tree (http://github.com/ry/node/commits/master/deps/v8) In an ideal world, you could have tagged a version of NodeJS source code with a particular version of V8 (which lives in a different repository), all under the same directory structure.

I did say it was for noobs. Main useful bits: * cheap host, $10/month, root access so no configuration headaches. My search didn't turn up many of those, and the node hosting wiki page is non-obvious: http://github.com/ry/node/wiki/Hosting/_edit (and only just added webbynode to the list) * how to set up that machine in particular * points to other helpful resources once node is installed

UTF8 seems to be the default encoding. I think he had just forgotten to update the docs for .write: http://github.com/ry/node/commit/7fc794a8ec55bd9d137c4888404...