[nodejs] Re: installation of nodejs doesn't include npm.

I was searching for an answer to that same problem and found your post. After looking for a while, I decided to install the only available version of npm(server) I could find (4.2.something) using zypper install nodejs-semver After that, I chose to ignore dependencies while installing npm with

[nodejs] @indutny :: Well done! #heartbleed

<http://blog.cloudflare.com/the-results-of-the-cloudflare-challenge> :-) -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google

[nodejs] TAGG: threads à gogo are back

Thanks to IngwiePhoenix (*) now TAGG builds properly again (with gyp, that is). npm install threads_a_gogo Enjoy the freedom of choice! (*) <https://github.com/IngwiePhoenix> -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/nod

Re: [nodejs] Re: Ben Noordhuis's Departure

On 09/12/2013, at 16:20, Mikeal Rogers wrote: > I haven't done any work for the node firm in a year. StrongLoop, according to > their own PR, is out of consulting and focused on their mBaaS. We're only > "rivals" if everyone doing node is a rival. I run a few conferences too, I'm > not a rival

Re: [nodejs] Re: Ben Noordhuis's Departure

On 09/12/2013, at 06:46, Mikeal Rogers wrote: > I don't work for Joyent. > > (...) > > If you want to take comments out of context to support some kind of Joyent > vs. StrongLoop world view it would be more effective to leave mine out of it > since I don't work for either. (...) You (and @izs

[nodejs] TFTP client and server

Hi, I was looking for an FTP client and then I was overtaken by a doubt... What are the uses of the *TFTP *protocol beyond router image loadings? It cannot be used by untrusted users, so it is basically used to move files from 2 machines inside a trusted environment. It is still useful in bash

Re: [nodejs] How to push a task to Nodejs' V8 main thread ?

On 26/09/2013, at 09:43, Ashish Negi wrote: > @Ben Thank you. It took me a while to understand what did you meant > "require() is not in global function". > > @Jorge Thank you too. After reading your post it hit me that i should do > global.request = request; > &g

Re: [nodejs] How to push a task to Nodejs' V8 main thread ?

*/ })(require, path, etc) ``` That's why it's in scope, but not because it's a global, it isn't. -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message be

Re: [nodejs] How to push a task to Nodejs' V8 main thread ?

On 26/09/2013, at 07:36, Ashish Negi wrote: > @Jorge Thanks but this also does not work the way i did it. > The final code that i gave the node to execute "from c++ addon" is : > >(function(){return this})().require = require; var fs = > require('f

Re: [nodejs] How to push a task to Nodejs' V8 main thread ?

ing::New(source.c_str(), sizeof(source) - > 1); > > > But still i can not use nodejs require function :( Put this in your main .js module, *before* the require() of your native .node module: (function(){return this})().require= require; Untested... -- ( Jorge )(); -- -- Job

Re: [nodejs] Re: Node.js should delete __proto__ while we still have a chance (before we hit 1.0)

tp://jsperf.com/homegrown-map-hash-vs-native Awesome :-) Thank you, -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodej

Re: [nodejs] Re: Node.js should delete __proto__ while we still have a chance (before we hit 1.0)

o it fails: > > > n['__proto__'] = "foo" > 'foo' > > n['__proto__'] > null > > WTF. That's still a problem. Object.create(null) solves nothing. > See Ben's message, that's currently the best way to workaro

Re: [nodejs] Re: Node.js should delete __proto__ while we still have a chance (before we hit 1.0)

> That's O(n) lookup time though - rather worse than the O(log n) or > O(1) characteristics of a JS dictionary. Yes, those `.indexOf(key)` can be a pain in the ass. -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mail

Re: [nodejs] Re: Node.js should delete __proto__ while we still have a chance (before we hit 1.0)

aren't safe, because what you get still has a working __proto__ -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups

Re: [nodejs] Re: Node.js should delete __proto__ while we still have a chance (before we hit 1.0)

its* __proto__ too. The ability to do that is in the table for ES.next, ISTM. Cheers, -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Goo

Re: [nodejs] Re: Node.js should delete __proto__ while we still have a chance (before we hit 1.0)

in hash true//What? 'console' in hash true//What? 'Array' in hash true//What? etc. -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you

Re: [nodejs] Re: When require() is slow: ideas on improving node.js require() performance on startup

On 30/07/2013, at 16:39, Ben Noordhuis wrote: > On Tue, Jul 30, 2013 at 3:45 PM, Jorge Chamorro > wrote: >> On 30/07/2013, at 11:52, Ben Noordhuis wrote: >>> >>> >>> Effective thread pool management is a topic of ongoing research but >>> it&#x

Re: [nodejs] Re: When require() is slow: ideas on improving node.js require() performance on startup

allel (to the same disk, of course). -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this

Re: [nodejs] Re: nodejs local variables

On 11/07/2013, at 10:31, Jean-Michel Hiver wrote: > basically "you can have global variables, private variables, but no proper > lexically scoped local variables". Much rather the opposite, what you haven't got is dynamic scoping. -- ( Jorge )(); -- -- Job Board: h

Re: [nodejs] Re: Private variables and setTimeout issue.

On 11/07/2013, at 23:13, Ben Noordhuis wrote: > On Thu, Jul 11, 2013 at 9:45 PM, Jorge Chamorro > wrote: >> On 11/07/2013, at 21:02, Jean-Michel Hiver wrote: >>> >>> >>>let foo = "bar"; >>> >>> Yields: >>>

Re: [nodejs] Re: Private variables and setTimeout issue.

scope- in the engines that have it: spidermonkey and perhaps (?) v8 with some runtime flag. -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subs

Re: [nodejs] Re: Private variables and setTimeout issue.

On 11/07/2013, at 20:40, Matt wrote: > On Thu, Jul 11, 2013 at 2:38 PM, Jorge Chamorro > wrote: >> >> Buuut... that has nothing to do with the problem of the OP > > You asked what hoisting has to do with it. Variables are hoisted to > file/function scope. Sayin

Re: [nodejs] Re: Private variables and setTimeout issue.

On 11/07/2013, at 19:16, Matt wrote: > On Thu, Jul 11, 2013 at 12:59 PM, Jorge Chamorro > wrote: >> >> Isn't that a convoluted way to say that in JS vars have function scope not >> block scope? > > Basically yes, though it has slightly more implications tha

Re: [nodejs] Re: Private variables and setTimeout issue.

On 11/07/2013, at 18:09, Matt wrote: > > On Thu, Jul 11, 2013 at 12:02 PM, Jorge Chamorro > wrote: >> On 11/07/2013, at 16:50, Matt wrote: >>> It's more a factor of hoisting not closures. >> >> What does hoisting have to do with that? > > The

Re: [nodejs] Re: Private variables and setTimeout issue.

On 11/07/2013, at 16:50, Matt wrote: > It's more a factor of hoisting not closures. What does hoisting have to do with that? -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You recei

Re: [nodejs] Re: Private variables and setTimeout issue.

); > }, 1000*i, item); > } Or: function log (item) { return function(){ console.log(item) } // or return console.log.bind(console, item) } for (var i=0; i Still I think the way closures works is a bug... Why? -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelin

Re: [nodejs] You're going to have to rewrite it anyway

ing on node.js but piss off people >> that are trying to make it conform with a lower level platform's >> packaging system, fuck em! > > This is outrageously stupid to say that. +1 -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https:

Re: [nodejs] Starting work on a Chrome Devtools addon

wser, or to debug a node remotely from the devtools of a chrome browser, or... Sorry if I'm being dense :-) Have you seen danny coates' node-inspector? Is it something like that? Cheers, -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.c

Re: [nodejs] Re: Limit of 32786 concurrent connections in a nodejs server

On 05/07/2013, at 00:38, Matt wrote: > 4 varies and is generally randomly chosen by the OS, but is in a fixed range > up to 32k 64k - 1024: the "well known tcp ports" are never used as ephemeral. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki

Re: [nodejs] Query length of event loop queue

o.github.com/e0b4108147b3fa603ef6badd805a2f01d73460fc/687474703a2f2f68746d6c352e6f687473752e6f72672f6e65775f736574496d6d6564696174655f73656d616e746963732e706e67 Wow, that's even beautiful! :-) -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posti

Re: [nodejs] Query length of event loop queue

r its .length was visible from user code. -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to t

Re: [nodejs] Re: [ANN] Ghost

Promises, promises... we'll see. On 19/05/2013, at 22:09, Nuno Job wrote: > Ghost is still active in kickstarter, it was an _idea_ just some months ago. > I saw it running already at John's computer but the code will be released > according to the kickstarter release schedule. I think that's Au

Re: [nodejs] child_process exec && spawn just hang

On 14/05/2013, at 17:01, alessioalex wrote: > Hey Jorge, I just tried that and it still hangs :( ORLY? Then I have no idea... ;-P Cheers, -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines

Re: [nodejs] child_process exec && spawn just hang

On 14/05/2013, at 16:18, alessioalex wrote: > Hey Jorge, > > The problem is that other commands work, event 'git shortlog' (when I add the > '--help' arg or another invalid argument). My problem is with 'git > --git-dir=/path/to/project/.git shortlog

Re: [nodejs] child_process exec && spawn just hang

> > exec('git --git-dir=/home/alessio/www/git-project/.git shortlog -sne', > function(err, stdout, stderr) { > console.log(arguments); > > }); > > > > Any suggestio

Re: [nodejs] tcp roundtrip time performance

is > reasonably low ( less than 50% on client and server, 4 cores ). Can anyone > explain what is the limit here - libuv, TCP stack, v8, ping script, CPU or > something else? > > [1] https://gist.github.com/sidorares/5573057 Sounds like if you were running out of ephemeral ports.

Re: [nodejs] Re: Our Contribution To Node Community, Introducing NodeJS Console

On 09/05/2013, at 21:18, Kushal Likhi wrote: > Hi, Great thanks for the feedback. > > • Security updates as mentioned by Jorge and Mikeal Rogers Where's the msg from Mikeal? Was it a PM? -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: http

Re: [nodejs] Re: Our Contribution To Node Community, Introducing NodeJS Console

in package.json, as > recommended by Stephen Belanger > • CoffeeScript file support, as recommended by Mark Hahn > • Ability to choose from Node version v0.10.5(latest), v0.8.21 and > v0.6.21 to run the script in. > • Security updates as mentioned by Jorge an

Re: [nodejs] Our Contribution To Node Community, Introducing NodeJS Console

ck your logs for details. I apologize :-) How does it do to deal -so well- with this sorts of things ? The attacks were affecting just me or the other users as well ? Cheers, (*) Got it from the "unix haters handbook" (**) Did you leave a gcc there on purpose? -- ( Jorge )(); --

Re: [nodejs] Node v0.9.9 (Unstable)

On 08/02/2013, at 23:45, Isaac Schlueter wrote: > On Fri, Feb 8, 2013 at 1:46 PM, Jorge Chamorro > wrote: >>> * addon: Pass module object to NODE_MODULE init function (isaacs, Rod Vagg) >> >> What does this mean exactly, please? > > It means that your ini

Re: [nodejs] Streams writev API

On 29/04/2013, at 00:14, Fedor Indutny wrote: > No, only TCP so far, but it could be implemented for FS too, pull requests > are welcome! :) Oh, what a pity... :-) And any of you have checked if Apple has fixed that bug already? -- ( Jorge )(); -- -- Job Board: http://jobs.node

Re: [nodejs] Streams writev API

On 29/04/2013, at 00:00, Fedor Indutny wrote: > It already landed in master and it works for every TCP socket. Awesome :-) What about fs? Cheers, -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Post

Re: [nodejs] Streams writev API

rhaps it shouldn't accept strings/encodings, just buffers: writev(buffer [, buffer...] [, cb]); The user can convert his strings to buffers quite easily already. Cheers, -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing

Re: [nodejs] Streams writev API

properly, which is a bit of a mess. -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post t

Re: [nodejs] Re: Retrieving values asynchroniously

w users to ask simple questions we need to > find a way to discourage this behavior. It is your behaviour what ought to be discouraged. Bye, -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You rece

Re: [nodejs] Re: correct way to read from a Readable stream

jklmNOPQRSTUVWXYZABCDEFGHIJKLM"; while (n < s.length) { r += ((pos = o.indexOf(t = s[n++])) >= 0) ? p[pos] : t; } return r; } -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines

Re: [nodejs] ANN: dicer

v1.1.9 (non-streaming): 3125.00 mb/sec > > > [1] https://github.com/mscdex/dicer I like it, it's awesome! -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message bec

Re: [nodejs] Re: $prefix/include/node/*.* headers missing in v0.10.x

On 03/04/2013, at 19:32, Nathan Rajlich wrote: > Jorge, would you like a pull request for TAGG to build with node-gyp? I > really don't understand your reluctance to give it a try, but I'll do the > dirty work for you if you'd rather. Are you kidding? Ye, *please* !

Re: [nodejs] $prefix/include/node/*.* headers missing in v0.10.x

On 03/04/2013, at 11:40, Ben Noordhuis wrote: > https://github.com/joyent/node/issues/5112 I'm in the "Saying 'just get used to our build system' is easy to say when you're not the one with an exiting build system" camp. -- ( Jorge )(); -- -- Job Board

Re: [nodejs] $prefix/include/node/*.* headers missing in v0.10.x

On 03/04/2013, at 11:40, Ben Noordhuis wrote: > On Wed, Apr 3, 2013 at 11:14 AM, Jorge Chamorro > wrote: >> I can't compile my module without headers... they're missing, is it a bug? > > No, it's intentional. How so? May I ask why? They used to come even wi

[nodejs] $prefix/include/node/*.* headers missing in v0.10.x

I can't compile my module without headers... they're missing, is it a bug? I want my money back! Cheers, -- ( Jorge )(); -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message becau

Re: [nodejs] How an event loop works

while (RUN) { dispatch setImmediateQueue(); dispatchPendingIO(); dispatchTimers(); dispatch nextTickQueue(); sleepPerhaps(); } -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message b

Re: [nodejs] How an event loop works

tchPendingIO(); dispatchTimers(); dispatch nextTickQueue(); } Please? TIA, -- Jorge. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodej

Re: [nodejs] Re: NodeJS analysis for suitability

> asynchronously from your main Node server. Or just write it in javascript, as a function, and run it in a thread-a-gogo. Simpler, faster and better. -- Jorge. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines

Re: [nodejs] Re: NodeJS analysis for suitability

On 15/02/2013, at 06:28, Prajwal Manjunath wrote: > Cluster was never meant to address the computation problems issue in Node. It > was simply meant to be something like a very basic Passenger/Unicorn load > distributor. https://gist.github.com/ry/2018811 -- Jorge. -- -- Job Bo

Re: [nodejs] NodeJS analysis for suitability

and that's what TAGG lets you do, within a single process, without the hassles of multiple processes + IPC + lost app's contexts to re-create. -- Jorge. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Gui

Re: [nodejs] How an event loop works

; Would love to get feedback on the post. The process.nextTick(ƒ) queue, more or less... :-) while (someThingToDo) { var n= nextTickQueue.length; while (n--) nextTickQueue.shift()(); var next_timeout = _run_timers(); if (nextTickQueue.length) continue; ms_sleep(next_ti

Re: [nodejs] NodeJS analysis for suitability

On 15/02/2013, at 10:02, greelgorke wrote: > > Am Freitag, 15. Februar 2013 07:08:44 UTC+1 schrieb Jorge: >> On 14/02/2013, at 20:28, Jacob Groundwater wrote: >> > >> > I think the solution to any CPU intensive task is a work queue. Do not mix >> > your

Re: [nodejs] NodeJS analysis for suitability

ne, a node with threads-a-gogo can do any amount of -javascript- CPU-bound tasks *and* any IO in parallel, easily and without sttutering, something that no node can do without threads-a-gogo. <https://github.com/xk/node-threads-a-gogo> -- Jorge. -- -- Job Board: http://jobs.nodejs.org/ Pos

[nodejs] Re: which is the best way to run tests?

Thanks everybody! I thought the commands you can run with npm are prefixed. I try some of the ways you say. Thank you very much! :) -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this messag

[nodejs] which is the best way to run tests?

hi, everybody. How do you run your tests in your projects? We want to run separately unit tests, integration tests and acceptance (service) tests. By now we are using "npm test" to run all together and "make test-unit", "make test-integration", "make test-acceptance" to run it separatly. We w

Re: [nodejs] Re: nodeconf videos?

On 08/02/2013, at 23:08, Mikeal Rogers wrote: > http://www.futurealoof.com Awesome, thanks for sharing, love @izs' idea of "no" :-) -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message becaus

Re: [nodejs] Re: nodeconf videos?

On 08/02/2013, at 22:55, Mikeal Rogers wrote: > Jorge, what conference do you run again? One that's so much better than the rest that doesn't even release any videos, hahaha. FYI: tenconf.s3.amazonaws.com is throttling -to Spain, at least- @ 20-25kB/s so it's ~ impossible

Re: [nodejs] Node v0.9.9 (Unstable)

On 07/02/2013, at 19:36, Isaac Schlueter wrote: > 2013.02.07, Version 0.9.9 (Unstable) Lovely! Thank you! > * addon: Pass module object to NODE_MODULE init function (isaacs, Rod Vagg) What does this mean exactly, please? Cheers, -- Jorge. -- -- Job Board: http://jobs.nodejs.org/ P

Re: [nodejs] Re: nodeconf videos?

came saying "(our)Conf was higher than almost anything we'd seen. (...) (our)Conf isn't like other conferences (...)" blah blah blah, but, @ JSConf there are many good talks and the videos are online... how's nodeconf any "higher" than that? -- Jorge. --

Re: [nodejs] Re: nodeconf videos?

>> @ JSConf they record and release all the talks: >> > > Yes, I know what other conferences do, especially JSConf's since I talk to > the organizers almost every day. Then you ought to ask them how do they do to record and release everything... -- -- Jo

Re: [nodejs] Re: nodeconf videos?

On 08/02/2013, at 22:08, Sara Chipps wrote: > Love when people get mad about the quality and availability of free things. Nodeconf? Was it free? Since when? -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You rec

Re: [nodejs] Re: nodeconf videos?

...) @ JSConf they record and release all the talks: <http://2012.jsconf.eu/speakers.html> Cheers, -- Jorge. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscr

Re: [nodejs] OpenEmbedded cross-building native libraries with node-gyp

__null, "/path/to/src.c", your_modules_entry_point, "your_modules_name" }; } Also once built you *can't* rename the your_modules_name.node to anything !== than the your_modules_name you passed to NODE_MODULE. hth, -- Jorge. -- -- Job Board: http://jobs.nodejs.org/ Posting guid

Re: [nodejs] OSX, a module, x86_64, i386, and a node compiled as a universal binary.

On 05/02/2013, at 20:29, Nathan Rajlich wrote: > Well v0.4.x is an even numbered release, so it is technically stable. I'm > sure some older running applications are still on those versions and that's > ok, they're just probably not going to be compatible with a lot of the newer > native addons

Re: [nodejs] OSX, a module, x86_64, i386, and a node compiled as a universal binary.

le built and ran fine until: - You broke the API for the umpteenth time again, and - You began distributing node as a universal binary which made that node-waf bug in your code -that you don't want to fix- bite. Thank you, it's always a pleasure to deal with you guys. :-( -- Jorge. --

Re: [nodejs] OSX, a module, x86_64, i386, and a node compiled as a universal binary.

On 05/02/2013, at 14:31, Jorge Chamorro wrote: > > > Did a google search and I (guess) I'd have to do what says here > <http://blog.omega-prime.co.uk/?p=102> in the "easy method", is that ~ right? > > So, how can I pass multiple arch flags from my ws

Re: [nodejs] OSX, a module, x86_64, i386, and a node compiled as a universal binary.

On 05/02/2013, at 17:55, Isaac Schlueter wrote: > Whoa, why are you looking in ~/.node_modules? What version of npm are > you using, 0.2.something? $ npm -v && node -v 1.2.2 v0.8.18 -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-

Re: [nodejs] OSX, a module, x86_64, i386, and a node compiled as a universal binary.

On 05/02/2013, at 17:54, Nathan Rajlich wrote: > Why do you *need* a fix for waf too? It's been deprecated for 2 major > releases now, and is completely removed from v0.9/v0.10. Currently my module can be installed in any node from v0.5.1 all the way up to the latest (0.8.18), and I'd like it t

Re: [nodejs] OSX, a module, x86_64, i386, and a node compiled as a universal binary.

ys here <http://blog.omega-prime.co.uk/?p=102> in the "easy method", is that ~ right? So, how can I pass multiple arch flags from my wscript ? Cheers, -- Jorge. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guide

Re: [nodejs] OSX, a module, x86_64, i386, and a node compiled as a universal binary.

On 05/02/2013, at 12:40, Fedor Indutny wrote: > Just use gyp ;) Thanks ;) but I need a fix for waf too... any ideas? Cheers, -- Jorge. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this mess

[nodejs] OSX, a module, x86_64, i386, and a node compiled as a universal binary.

86_64): Mach-O 64-bit executable x86_64 If he then installs a module, for some reason (*) waf chooses to make it for i386 only: $ npm install threads_a_gogo ... $ file /Users/jorge/.node_libraries/threads_a_gogo.node /Users/jorge/.node_libraries/threads_a_gogo.node: Mach-O bundle i386 Then he&#x

[nodejs] Threads_a_gogo updated to 0.1.5

ags, e.g. .create('--expose_gc --harmony_modules'), per thread. <http://github.com/xk/node-threads-a-gogo> Enjoy, -- Jorge. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because y

Re: [nodejs] Fujitsu's new proprietary protocol claiming 30x speed of TCP

diots? -- Jorge. On 31/01/2013, at 10:14, Mark Hahn wrote: > In order to be faster by 30X, the current tcp would have to only be using 3% > of the bandwidth. Kind of ridiculous. > > > On Wed, Jan 30, 2013 at 8:23 PM, Thomas Shinnick wrote: > To the extent that it sounds like

Re: [nodejs] Running javascript code "safely"

27; + clientProcedure + ')(' + data + ')', cb); function cb (result) { //here you'd receive the result of clientProcedure(data); aThread.destroy(); } -- Jorge. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-Lis

Re: [nodejs] Node v0.8.17 (Stable)

time out/Release/node tmp/http-chunked-client.js > real0m5.386s > user0m2.768s > sys 0m0.728s > >That's still a 185x speed-up. That's awesome, well done! Congratulations, -- Jorge. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: htt

Re: [nodejs] Re: Does clearTimeout remove an unprocessed callback which is already in the execution queue?

Not-in-a-spec is !== indeterminate. All the browsers do it right, even though it's not in any w3c spec. There's many many other things in the browsers that aren't (or weren't until recently) in any spec. De-facto standard behaviours, if you will. -- Jorge. On 13/12/2

Re: [nodejs] Re: Does clearTimeout remove an unprocessed callback which is already in the execution queue?

console.log("hello world"); >> }, 0); > > No. The order in which the timer callbacks run is unspecified, same > as for browsers. The browsers, *all* the browsers in the world, run t1 before t2, unlike node. If you ever find one that doesn't please let me kn

Re: [nodejs] "this" and that

a bunch of them in node, try threads-a-gogo: <http://www.google.com/search?q=TAGG+threads+in+node> Cheers, -- Jorge. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subsc

Re: [nodejs] "this" and that

On 13/12/2012, at 01:47, Rick Waldron wrote: > > On Wed, Dec 12, 2012 at 7:20 PM, Jorge Chamorro > wrote: > On 12/12/2012, at 18:37, Rick Waldron wrote: > > Runtime code generation? new Function( thecode ) works just as well, I guess > > ...sometimes: > &g

Re: [nodejs] "this" and that

On 13/12/2012, at 01:47, Rick Waldron wrote: > > On Wed, Dec 12, 2012 at 7:20 PM, Jorge Chamorro > wrote: > On 12/12/2012, at 18:37, Rick Waldron wrote: > > > > On Wed, Dec 12, 2012 at 2:17 AM, Isaac Schlueter wrote: > > On Tue, Dec 11, 2012 at 7:18 PM, spqr

Re: [nodejs] "this" and that

st be backwards compatible forever. > > > Runtime code generation? new Function( thecode ) works just as well, I guess ...sometimes: (function (p) { eval("(function(){console.log(p)})")(); try { Function("console.log(p)")(); } catch (e) { console.log

Re: [nodejs] What's the default value for buffer

memory is continually reused so it may as well contain data from any other connection. On 08/12/2012, at 06:53, Mark Hahn wrote: > I would guess the rule is that there is no rule. > > On Fri, Dec 7, 2012 at 6:13 PM, Goddy Zhao wrote: >> var buf = new Buffer[1]; >> console.log(buf[0]); >> >>

[nodejs] Re: Unable to send millisecond timeout.

clamping (the browsers clamp it to a minimun of several ms, mainly due to a bug in jquery). But, the setTimeout(ƒ,1) behaving as a setTimeout(ƒ,0) is *clearly* a bug. Node's timers have always been buggy -and still are- for example this: setTimeout(a,10), setTimeout(b,10) may fire a then b

[nodejs] Re: process.env - documentation?

On 31 oct, 17:26, Scott Elcomb wrote: > On Wed, Oct 31, 2012 at 10:59 AM, Jorge > > wrote: > > On Oct 31, 2:04 pm, Bgsosh wrote: > >> Hi, I'm tring to understand the structure of the process.env object, but > >> the online docs just say 'An

[nodejs] Re: process.env - documentation?

f a giga- byte by specifying a number followed by ``G'' or ``g''. Sizes less than 512 bytes or greater than a gigabyte are ignored. EXINIT A startup list of commands read by ex(1), edit(1), and vi(1). ... -- Jorge. -- Job Board

Re: [nodejs] nodejs zlib performance

hing that unnerves more than one here. Or not? Cheers, -- Jorge. On 25/10/2012, at 23:24, Isaac Schlueter wrote: > Jorge, > > Please do not make snarky remarks about Node on this mailing list. If > you have a problem with something, bring it up in a new thread. If > you have

Re: [nodejs] nodejs zlib performance

Are you saying that node, internally, delegates CPU intensive work to background threads? Heresy! -- Jorge. On 25/10/2012, at 23:22, Vadim Antonov wrote: > We don't use threads by ourselves. It's default nodejs zlib library > implementation. > -- > Vadim > > On

Re: [nodejs] nodejs zlib performance

Threads are evil™, don't use threads. The Node Way® (just don't ask) is to pipeline processes as in the good ol' 70s. Flower Power, peace and love bro, and etc. Cheers, -- Jorge. On 25/10/2012, at 19:24, Vadim Antonov wrote: > There're 8 processes (1 per core, create

Re: [nodejs] Re: Threading, and Dogmatisms.

On 18/09/2012, at 00:14, Mikeal Rogers wrote: > Jorge, > > This is me asking you nicely to stop. You've succeeded in making some of the > most level headed and accommodating people in the community scream. Great > work, job well done. Time to stop now. > > If you

Re: [nodejs] Re: Threading, and Dogmatisms.

run them? eval(program); As simple as that! E.g., REPL: Read Eval Print Loop. I chose to use thread.eval(program) because eval() -as the threads- is evil. Will alias it as thread.evil(program) in the next release, just so it's absolutely clear. :-P -- Jorge. -- Job Board: http:/

Re: [nodejs] Threading, and Dogmatisms.

On 17/09/2012, at 22:09, Ben Noordhuis wrote: > On Mon, Sep 17, 2012 at 11:39 AM, Jorge wrote: >> On the other hand it didn't take too long for the V8 guys to fix exactly >> that in the isolates branch... > > That's actually a good example of the cost of thre

Re: [nodejs] Memory leak, growing RSS and debugging

ms start to *really* use that memory, then, the OS *may* need to start swapping pages to/from disk like crazy, or not, it depends: if the combined *real* usage is > phisical RAM it will swap, if it isn't, it won't. -- Jorge. -- Job Board: http://jobs.nodejs.org/ Posting guidelines

Re: [nodejs] Threading, and Dogmatisms.

On 17/09/2012, at 11:12, Ben Noordhuis wrote: > On Mon, Sep 17, 2012 at 10:49 AM, Jorge wrote: >> On 17/09/2012, at 06:35, Ben Noordhuis wrote: >> >>> (...) >>> That small gain is offset by the need to serialize access to your data >>> structures - wh

Re: [nodejs] Crockford : Ynode : "I would fork node.js"

ers. Why? I don't know. But it *should*. DART provides an isolates class for that: <http://api.dartlang.org/docs/continuous/dart_isolate.html> -- Jorge. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines

  1   2   3   >