I'm a node newb and I don't know enough to make my own judgments between
various (generally very professionally written) frameworks/libs. I rely on
the wisdom of the community and generally my first step in researching a
solution is to search github and order by most stars. I then google to be
Using callbacks in your own application code is the path of least
resistance for using the majority of value in the node ecosystem.
I am new to Node and trying to decide between promises, asynch and vanilla,
there are so many good arguments for each. Mikeal, do you mind expanding
further
I have to say this post scares me a little. You are trying to get node
running on one very old OS with a huge security risk. It's not even funny.
You'd be better off taking the machine and putting Unbuntu on it or ANY
other current OS.
On Wed, May 22, 2013 at 9:19 PM, Bert Belder
is there a resource somewhere that lists the most popular libs by useful
categories?
The closest thing I know of is to work down NPM's most depended on list
(https://npmjs.org/browse/depended), for each package, you can look at the
description and keywords to get a sense of what the category
I'm writing a asynchronous Node Addon, but I have been struggling to figure
out if I need to use a HandleScope in the After function that calls the
client JavaScript callback. I've seen examples showing with and without new
scopes, but never any explanation why. Here is an example:
void
the code:
var http = require('http');
http.createServer(function (req, res) {
console.log(req.url);
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('Hello World\n');}).listen(1337);
console.log('Server running at 1337');
I install the node-v0.6.18 on window7 and linux
cat
On Thu, May 23, 2013 at 4:44 AM, Cecil Rock cecil.r...@gmail.com wrote:
I'm writing a asynchronous Node Addon, but I have been struggling to figure
out if I need to use a HandleScope in the After function that calls the
client JavaScript callback. I've seen examples showing with and without new
On Thu, May 23, 2013 at 3:29 AM, Baz b...@thinkloop.com wrote:
I am new to Node and trying to decide between promises, asynch and
vanilla, there are so many good arguments for each. Mikeal, do you mind
expanding further how using promises in your own, non-shared, code could
hinder use of
On May 23, 2013, at 02:37, cheng cao wrote:
I install the node-v0.6.18 on window7 and linux
That's old. Please try 0.10.7.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you
I am not. Can you give me some hints what this session middleware should be?
On Wednesday, May 22, 2013 5:25:54 AM UTC-7, mscdex wrote:
On May 22, 1:19 am, Toddy Mladenov m...@toddysm.com wrote:
It seems the session object is not created but I have no idea why.
Shouldn't this be created
The best rating I know https://github.com/languages/JavaScript/most_watched
By the way, not only for JS but for other langs too, usually, when I need
something and don't know where to start - I start there, and after reading
3-10 pages found all major solutions for my problem.
I don't like
On May 23, 11:35 am, Toddy Mladenov m...@toddysm.com wrote:
I am not. Can you give me some hints what this session middleware should be?
Just look at the order of your `app.use()` calls.
According to passport's site, the order should be something like this:
app.configure(function() {
Thanks Matt, so just to be crystal clear, if I'm using promises in my own
code, then I happen to have a flow that depends on fs, for example, and
since fs doesn't return or use promises, I would have to drop out of the
promises paradigm and manage that particular part of the flow control with
That's overstating it a bit. It's very easy to convert to promise-based code,
e.g.:
var fs = require('fs');
var Q = require('q');
var readFile = Q.denodeify(fs.readFile);
var writeFile = Q.denodeify(fs.writeFile);
readFile('src.txt').then(function (result) { writeFile('dest.txt', result);
On May 23, 2013, at 1:28 PM, Baz b...@thinkloop.com wrote:
Thanks Matt, so just to be crystal clear, if I'm using promises in my own
code, then I happen to have a flow that depends on fs, for example, and since
fs doesn't return or use promises, I would have to drop out of the promises
Thank you gents, perfectly got it now.
On Thu, May 23, 2013 at 10:42 AM, // ravi ravi-li...@g8o.net wrote:
On May 23, 2013, at 1:28 PM, Baz b...@thinkloop.com wrote:
Thanks Matt, so just to be crystal clear, if I'm using promises in my
own code, then I happen to have a flow that depends on
The most_watched https://github.com/languages/JavaScript/most_watched list
is awesome. Thanks for the tip.
On Thu, May 23, 2013 at 8:42 AM, Alexey Petrushin
alexey.petrus...@gmail.com wrote:
The best rating I know
https://github.com/languages/JavaScript/most_watched
By the way, not only
There's also nipster (http://jiyinyiyong.github.io/nipster/), which combines
github rankings with npm packages.
-- peter
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you
Alex,
I think that's an awesome idea. But...a) I stink at node b) probably don't
have time to devote to help beyond complaints/a list of what I'd like to
see c) I'm full of excuses.
There is Mike Brevoort's node-reggie -
https://github.com/mbrevoort/node-reggie (I keep name dropping that hoping
I'm new to node and I am investigating using node for a non-web
always-blocking cpu-intensive high-memory process. The process basically
runs in an infinitely loop, loading a lot of data from a datastore into
memory, applying complex (blocking) business logic, then saving the result
back to the
20 matches
Mail list logo
