node-v0.x-archive

Direct link to a list of changes you have to make to your codebases: https://github.com/joyent/node/wiki/API-changes-between-v0.4... Question: Since this doesn't look that complex, is anyone working on an automagical translator from 0.4 to 0.6 that people could use?

(I assume) the reason that node chose to go with a single global object (which is optional[0]) is that JS gets a bit hinky when dealing with multiple contexts: e.g., an array returned from a function defined in a different context will not satisfy `[] instanceof Array`, since the receiving module's instance of `Array` is not strictly equal to to called module's copy of `Array`. In practice, this problem is why you see `Array.isArray`, `jQuery.isArray`, `_.isArray` and friends so often -- they exist to give a canonical, non-"check if any member of X's inheritance chain matches Y.prototype" way to determine if a given instance is actually an array. So, in summation: yes, it's weird that Node has this, but ultimately it's a lesser-vilified problem of JavaScript's. [0]: https://github.com/joyent/node/blob/master/lib/module.js#L51 -- `NODE_MOD

There certainly is no shortage of other options: https://github.com/joyent/node/wiki/modules#wiki-web-framewo...

Yes :) Still waiting for a proper execSync ( https://github.com/joyent/node/issues/1167 ). Without it small build/utility scripts turn into macaroni cheese unless you resort back to Python/Ruby/Bash - more languages, harder to maintain.

It's unfortunate this doesn't just use JSGI, which is much closer to Rack/WSGI than Connect, and has a fair amount of usage in Node (https://github.com/joyent/node/wiki/modules#wiki-middleware-...), as well as other server-side JavaScript platforms (Ringo, Akshell, Pintura, Narwhal) I'd love to hear the reasoning for the differences between the two. (Disclaimer: I started JSGI)

Clearly mountains out of mole hills Best Comment: @chjj "Is it me, or is this argument over a single colon?" https://github.com/joyent/node/pull/1580#issuecomment-192688...

Here's a good list of available modules https://github.com/joyent/node/wiki/modules. If you get involved in the community you'll quickly discover which ones are widely used in your area of concern. I've played with express http://expressjs.com/ routing and views with the jade https://github.com/visionmedia/jade view engine. I found them quite easy to learn. When I got into node I also got into MongoDB http://www.mongodb.org/ so I haven't played with any ORM tools because there was no mapping of objects to a relation db needed, no mapping at all really since I pretty much keep everything in JSON format from front to back.

You could write your own way of doing it or use an existing flow control library. There are lots. :) https://github.com/joyent/node/wiki/modules#wiki-async-flow For a specific example, look at async.parallel: https://github.com/caolan/async

I'd say it's pretty far along: https://github.com/joyent/node/wiki/modules

Exceptions are interesting. The calls are asynchronous so you can't wrap the whole macro in a single try/catch. See node's wiki for an explanation on why this is a problem: https://github.com/joyent/node/wiki/Async-exception-handling Node encourages people to create functions like: function(err, x) { if(err) handle(err); } This way they avoid the whole async + try/catch problem. It should be possible to define a macro that does something similar. Avoiding that trap, individual try/catch statements still work fine: (timeout/timeout-macro (pn "Hello") (try* (pn (throw "Throwing up")) (catch e (pn (str "There was an error: " e)))) (pn "World"))

Could the work being done for porting nodejs to windows[1] be used for a nginx's windows port in any way ? [1]https://github.com/joyent/node/tree/master/deps/uv