Car.prototype.appeal = appeal;
function is outside prototype, which slowed the process
http://jsperf.com/prototypemodule-vs-closuremodule/10
but it seems thats better for closure
http://jsperf.com/prototypemodule-vs-closuremodule/11
jules
--
Job board: http://jobs.nodejs.org/
New group
Le lundi 12 janvier 2015, 17:00:21 Alexander Praetorius a écrit :
> Maybe that test has to be refined?
like this?
http://jsperf.com/prototypemodule-vs-closuremodule/6
v8 made some optimizations on "prototype" way
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/ot
er 2013 00:08:00 UTC+2, Aria Stewart wrote:
>
> Are you subclassing EventEmitter yourself?
>
>
> Jules > wrote:
>>
>> I wonder if this might be a bug in Node.
>>
>> The only call to process.nextTick in the stack trace is here:
>> https://github.
I wonder if this might be a bug in Node.
The only call to process.nextTick in the stack trace is here:
https://github.com/joyent/node/blob/v0.10.12/lib/_stream_writable.js#L258
Or perhaps we're misusing Sockets somehow.
Stack trace follows:
Trace: (node) warning: Recursive process.nextTick de
Thanks - "--trace-deprecation" sounds like a great place to start.
On Monday, 9 September 2013 09:44:49 UTC+2, Jules wrote:
>
> Since upgrading from 0.8 to 0.10, we're occasionally see these crashes in
> production:
>
> (node) warning: Recursive process.nextTic
mum call stack size exceeded
The weird thing is, courtesy of grep I'm confident that we do not utilize
process.nextTick anywhere; neither in our code nor in any modules we use.
Any advice on figuring this one out?
We're on node v0.10.12
Cheers,
Jules
--
--
Job Board: http:
Modules that contain compiled C++ code need to be rebuilt when the Node
version changes, right?
Any suggestions on ways to automate this? We're chef-managed, but can't
seem to find a way to trigger* npm rebuild* after a Node upgrade.
Is there any way to determine the linked-against version of
The recommended pre-built package for CentOS (according to nodejs.org)
is http://nodejs.tchol.org/
But these appear stuck on v0.6. Their mailing lists don't mention any
upcoming upgrades
Any ideas if this will happen, or when, or if there is a better repo that
CentOS / RHEL/ AMZN users should
Daemon A needs to push lots of data to Daemon B, which is located on
another continent. The bandwidth available is usually quite high, but
it's highly variable and might drop out entirely at times.
Is there an accepted "best strategy" for implementing this in Node?
Does A just write as fast as i
