Re: [nodejs] Re: Giving up on node.js / Flatiron / hook.io
Nathan - My intention was to inform the community I would no longer be maintaining a lot of projects that many developers communicate with me about on a semi-frequent basis. The alternative would have been to silently stop supporting these projects ( disappear ) without any notice or explanation. - Marak On Wed, Sep 12, 2012 at 10:17 PM, Nathan White changereal...@gmail.comwrote: I usually refrain from this bs but when people start asking for explanations about such absurdities I find it very hard to refrain. Marak's behavior is childish and deserves no explaination. The way he brought this shit to the forum should signal why he was fired. None of these issues should take away from all the other talented members of nodejitsu. It doesn't matter if Marak is right, to handle an issue like this in a public forum is inexcusable. On Sep 12, 2012, at 10:33 PM, Adam Crabtree atcrabt...@gmail.com wrote: When a leader departs from a community like this, a reasonable explanation helps answer the most basic questions that are on everyone's minds, while setting expectations of privacy in what they chose not to share. We should respect that and appreciate Marak's willingness to share personal details for the sake of greater clarity. Dramatic or not, none of us knows unless we know the whole story, which Marak chose not to share. Consider reaching out to Marak privately to encourage him in what is obviously a less than ideal situation. Otherwise, let's do as Mikeal suggests. Cheers, Adam Crabtree On Wed, Sep 12, 2012 at 12:46 PM, Micheil Smith mich...@brandedcode.comwrote: Really, that was just me getting a wee bit annoyed at the idea of the whole dramatisation here. If a company fires you, they either had a reason to, or, you have a lawsuit you can probably press, if you really want to. No need to make a big noise about it and try to paint them out as evil or wrong or whatever, it's fine though if someone asks that you're honest about it, but do we really need to discussion or even here about Marak's firing on the Node.js mailing list? As far as I'm concerned, not really, no. – Micheil On 12/09/2012, at 6:43 PM, Mikeal Rogers wrote: It is beyond foolish to speculate about why someone was fired from an announcement like this. I suggest you ask Marak or someone else at nodejitsu you know personally why this happened if you find it necessary to gossip. -Mikeal On Sep 12, 2012, at September 12, 201210:41 AM, Micheil Smith mich...@brandedcode.com wrote: Wasn't wanting to add into this, but reading between the lines it reads as if there was a conflict of interest, Marak was developing something open-source that was seen as a potential competitor to the closed-source product he was being paid to work on. Which, if he wished to not stop work on that potential competitor, then sure, sounds fine to dismiss him from the position he held at the company. And then, all that aside, I can understand being angry at a company, but the tone of that email was way off. Sure, if people ask you directly as to why, you can say something to them about it, but no need to make a massive show out of it. – Micheil On 12/09/2012, at 4:54 PM, Jeff Barczewski wrote: Yes, it would be beneficial for both sides to communicate a summary of what transpired to get to this point, rather than leaving this nebulous cloud over everything. Marak, have you looked into those companies that were trying to hire Node developers? (If moving is an option, then NodeUp sponsors like Clock and Bislr are a few that come to mind) On Wednesday, 12 September 2012 10:43:15 UTC-5, Zeus wrote: So what was Nodejitsu's reasoning in all this? Your tone make it seem you feel that they fired you unjustly. Best, Zeus -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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] Re: Node.js - authentication - Django
well if your django app handles auth already, you can handle it than through token bypassing i.E. through a persistent session store or something like that. django stores the session in a key-val store, your node app fetches this session and check it for auth token. or you expose a rest-service from your django app, so node can ask you main app for authentication state. the socket.io connection is opened when on client side io.connect is called and accepted by server. Am Mittwoch, 12. September 2012 22:59:02 UTC+2 schrieb refreegrata: Thanks for the reply. Python with Socket.io is an option. I thought in that too. My doubt is about the webserver... comments and reviews in Internet says that Apache isn't good with multiple connections. Maybe in my application have just a few of users. In fact, just between 10-15, but in the future (three - six months) I must to add some others elements based in socket.io, and will arrive a lot of users. Also, another important information: We don't have enormous servers (x32, 4GB RAM, P4) and we aren't in position to buy bigger equipment promptly. For that I'm thinking in node.js, for their recognized performance with very dinamic systems. On Wednesday, September 12, 2012 3:26:33 AM UTC-3, greelgorke wrote: may be its not a good idea to start a node.js just for real-time updates. you can use plain socket.io for it. here are infos about a python implementation http://stackoverflow.com/questions/4762086/socket-io-client-library-in-pythonand http://blog.pythonisito.com/2011/08/websockets-to-socketio.html good luck Am Dienstag, 11. September 2012 21:30:34 UTC+2 schrieb refreegrata: Hello list. I'm new here. A totally newbie trying to learn. I have a web application for internal use and developed with Django and running over Apache. In the app the access to every section is avaliable only for authenticated users with permissions over the view (except for the login). For this I use the authentication module provided for Django. The basic usage used for me is something like: @decorator_to_check_permission def my_view(request .. Now I must to create a section with multiple data and a lot of references and a lot of ajax. The section is almost finished. Just need one more thing. The info in the page can be edited by multiple users. If an user edit some section the other user must to refresh the page (or only a section with ajax) to see the changes. Well, this is ugly. For that I want to use node.js, just for this section inside the page. Learn about Comet and programming this. Timers+Ajax or hidden Iframes aren't in my plans. Now my question. Are any way to check if the user is authenticated and if have the permissions to get responses from node.js? Can I use the same authentification from Django or I must to use another authentification module from node.js? When the connection is opened? As you can see, i'm a little loss with this. Maybe my question is stupid or not logical, but I don't know... the change isn't easy ...at least for me. Bye, Cheers P.D.: Sorry for my english. Is ugly and rough. -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Beginner question about async function inside another function
got it why is the first parameter of the callback null in cb(null, files); ? thank you António 2012/9/11 Elliot efos...@firetaco.com If you're only doing it on startup, you could also use the synchronous version of readdir. On Sep 11, 2012 7:27 AM, Mark Volkmann r.mark.volkm...@gmail.com wrote: -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Beginner question about async function inside another function
Convention is for the first argument to callbacks to be an error description. If there was no error, null is passed. --- R. Mark Volkmann Object Computing, Inc. On Sep 13, 2012, at 3:58 AM, António Ramos ramstei...@gmail.com wrote: got it why is the first parameter of the callback null in cb(null, files); ? thank you António 2012/9/11 Elliot efos...@firetaco.com If you're only doing it on startup, you could also use the synchronous version of readdir. On Sep 11, 2012 7:27 AM, Mark Volkmann r.mark.volkm...@gmail.com wrote: -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Anonymous functions garbage collection
It is a pretty typical approach to use an anonymous function for
asynchronous calls from inside a loop:
var a = getInitialData();
for (var i = 0, len = a.length; i len; i++) {
(function(el) {
/* do something non-blocking here */
})(a[i]);
}
JSLint doesn't like this code with Don't make functions within a loop
warning, and it is actually right since it really creates a new anonymous
function on every single loop iteration. An obvious solution is to declare
this function outside a loop, but it would make a code less readable. Even
if a declaration would just precede the loop: you see a call here, you see
a declaration somewhere else, and here you are, lost all your attention.
My question is how bad this approach is for an overall performance? In
particular, how fast and efficient a garbage collection of anonymous
functions is? How much memory a typical anonymous function can consume and
how long it may exist in a memory?
--
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 group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Build error while installing nodemailer on Win 7
I had something similar after I installed vs 2012 preview. This article should give you enough info to sort it http://social.msdn.microsoft.com/Forums/en-US/tfsbuild/thread/9055ca52-586b-459f-9dd1-a9d052d076b9/ -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Giving up on node.js / Flatiron / hook.io
Marak, For the record I think your a pretty cool guy I just don't agree with your actions. You have let your ego distort the lens of reality. I, like yourself am very much a risk taker. With risks there are successes and failures. Look forward not backwards. It is admiral to inform the community about your changing involvement on projects. This has been the guise of this thread but not the true motive. People have asked if you will transfer ownership, with no response. There is a reason github made this a core feature. We all thank you for your involvement and wish you the best of luck in your future endeavors. Visions, strategies and goals change at companies all the time, especially startups. It is obvious that your not in alignment with your previous employer. Remember there are many other people involved in building companies. Teams need unity not discord. Companies must remove barriers to unity, sometimes it people. It's not about who is right or wrong, it just is. Move on. Put your talents to use, you should have no problem finding a paycheck. The self loathing will get you nowhere. On Sep 13, 2012, at 12:03 AM, Marak Squires marak.squi...@gmail.com wrote: Nathan - My intention was to inform the community I would no longer be maintaining a lot of projects that many developers communicate with me about on a semi-frequent basis. The alternative would have been to silently stop supporting these projects ( disappear ) without any notice or explanation. - Marak On Wed, Sep 12, 2012 at 10:17 PM, Nathan White changereal...@gmail.com wrote: I usually refrain from this bs but when people start asking for explanations about such absurdities I find it very hard to refrain. Marak's behavior is childish and deserves no explaination. The way he brought this shit to the forum should signal why he was fired. None of these issues should take away from all the other talented members of nodejitsu. It doesn't matter if Marak is right, to handle an issue like this in a public forum is inexcusable. On Sep 12, 2012, at 10:33 PM, Adam Crabtree atcrabt...@gmail.com wrote: When a leader departs from a community like this, a reasonable explanation helps answer the most basic questions that are on everyone's minds, while setting expectations of privacy in what they chose not to share. We should respect that and appreciate Marak's willingness to share personal details for the sake of greater clarity. Dramatic or not, none of us knows unless we know the whole story, which Marak chose not to share. Consider reaching out to Marak privately to encourage him in what is obviously a less than ideal situation. Otherwise, let's do as Mikeal suggests. Cheers, Adam Crabtree On Wed, Sep 12, 2012 at 12:46 PM, Micheil Smith mich...@brandedcode.com wrote: Really, that was just me getting a wee bit annoyed at the idea of the whole dramatisation here. If a company fires you, they either had a reason to, or, you have a lawsuit you can probably press, if you really want to. No need to make a big noise about it and try to paint them out as evil or wrong or whatever, it's fine though if someone asks that you're honest about it, but do we really need to discussion or even here about Marak's firing on the Node.js mailing list? As far as I'm concerned, not really, no. – Micheil On 12/09/2012, at 6:43 PM, Mikeal Rogers wrote: It is beyond foolish to speculate about why someone was fired from an announcement like this. I suggest you ask Marak or someone else at nodejitsu you know personally why this happened if you find it necessary to gossip. -Mikeal On Sep 12, 2012, at September 12, 201210:41 AM, Micheil Smith mich...@brandedcode.com wrote: Wasn't wanting to add into this, but reading between the lines it reads as if there was a conflict of interest, Marak was developing something open-source that was seen as a potential competitor to the closed-source product he was being paid to work on. Which, if he wished to not stop work on that potential competitor, then sure, sounds fine to dismiss him from the position he held at the company. And then, all that aside, I can understand being angry at a company, but the tone of that email was way off. Sure, if people ask you directly as to why, you can say something to them about it, but no need to make a massive show out of it. – Micheil On 12/09/2012, at 4:54 PM, Jeff Barczewski wrote: Yes, it would be beneficial for both sides to communicate a summary of what transpired to get to this point, rather than leaving this nebulous cloud over everything. Marak, have you looked into those companies that were trying to hire Node developers? (If moving is an option, then NodeUp sponsors like Clock and Bislr are a few that come to mind) On Wednesday, 12 September 2012 10:43:15 UTC-5, Zeus
Re: [nodejs] Anonymous functions garbage collection
I don't see any problem with your approach, and I would probably have
done the same. Yet, JSLint would remind about making functions within
loop. Well, should not matter unless you're looping over arrays with
/some/ thousands elements.
As an alternative, if code readability/simplicity is a concern, why not
go with async https://github.com/caolan/async?
var execute = function (item, cb) {
/* do something meaningful with item, fire cb when done */
};
var arr = getInitialData();
async.forEach(arr, execute, function (err) {
// check for error and/or proceed further
});
You could use one of many available control flows, check out many more
control flows https://github.com/caolan/async/blob/master/README.md.
The advantage is the package provides different control flows without
having to keep re-inventing them. Say, you want to perform certain
activity in parallel, or in series, or based on some conditionals, while
we could write code to achieve that, I would recommend using async as it
is well written and thoroughly tested https://npmjs.org/package/async
piece of code.
Where you want to place the execute code depends on many factors, like
do we need to access/modify other variables in scope, if independent
operations, they can go in library functions.
Please share your thoughts.
On 09/13/2012 11:30 AM, Maxim Kazantsev wrote:
It is a pretty typical approach to use an anonymous function for
asynchronous calls from inside a loop:
var a = getInitialData();
for (var i = 0, len = a.length; i len; i++) {
(function(el) {
/* do something non-blocking here */
})(a[i]);
}
JSLint doesn't like this code with Don't make functions within a
loop warning, and it is actually right since it really creates a new
anonymous function on every single loop iteration. An obvious solution
is to declare this function outside a loop, but it would make a code
less readable. Even if a declaration would just precede the loop: you
see a call here, you see a declaration somewhere else, and here you
are, lost all your attention.
My question is how bad this approach is for an overall performance? In
particular, how fast and efficient a garbage collection of anonymous
functions is? How much memory a typical anonymous function can consume
and how long it may exist in a memory?
--
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 group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
--
Regards,
Vinayak
--
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 group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] `npm install -g .`, but faster...
I have a node project I'm working on that I frequently install with `npm install -g .` before running tests and such against the installed executable. When I do this, there's always a few seconds of waiting for npm to establish dependencies and do whatever else it does under the hood. I was wondering if there was a faster way to do this? Is there some option I can use to have npm forgo checking for depdendencies and just install my module locally without any other checks? -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Anonymous functions garbage collection
well. you have to understand why this is done in this way. the immediate
function is used here to create scope, so every closure created has access
to the right value. w/o this construct every of all a.lenght clojures will
acces the same value: a[a.length-1].
i do not agree that defining a function somewhere else decrease
readability, its the opposite. if i declare well named, pure function i
increase readability, plus, reusability, reduce my memory footprint and
garbage collection effort.
Am Donnerstag, 13. September 2012 08:00:42 UTC+2 schrieb Maxim Kazantsev:
It is a pretty typical approach to use an anonymous function for
asynchronous calls from inside a loop:
var a = getInitialData();
for (var i = 0, len = a.length; i len; i++) {
(function(el) {
/* do something non-blocking here */
})(a[i]);
}
JSLint doesn't like this code with Don't make functions within a loop
warning, and it is actually right since it really creates a new anonymous
function on every single loop iteration. An obvious solution is to declare
this function outside a loop, but it would make a code less readable. Even
if a declaration would just precede the loop: you see a call here, you see
a declaration somewhere else, and here you are, lost all your attention.
My question is how bad this approach is for an overall performance? In
particular, how fast and efficient a garbage collection of anonymous
functions is? How much memory a typical anonymous function can consume and
how long it may exist in a memory?
--
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 group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: `npm install -g .`, but faster...
this might help to reduce latency http://node-code.com/blog/?p=155 it's about local npm repository Am Donnerstag, 13. September 2012 16:37:35 UTC+2 schrieb Tony Lukasavage: I have a node project I'm working on that I frequently install with `npm install -g .` before running tests and such against the installed executable. When I do this, there's always a few seconds of waiting for npm to establish dependencies and do whatever else it does under the hood. I was wondering if there was a faster way to do this? Is there some option I can use to have npm forgo checking for depdendencies and just install my module locally without any other checks? -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: `npm install -g .`, but faster...
so not a flag to npm then? :-) I'll give this a shot later on and see if it helps. Thanks for the tip. On Thursday, September 13, 2012 10:56:55 AM UTC-4, greelgorke wrote: this might help to reduce latency http://node-code.com/blog/?p=155 it's about local npm repository Am Donnerstag, 13. September 2012 16:37:35 UTC+2 schrieb Tony Lukasavage: I have a node project I'm working on that I frequently install with `npm install -g .` before running tests and such against the installed executable. When I do this, there's always a few seconds of waiting for npm to establish dependencies and do whatever else it does under the hood. I was wondering if there was a faster way to do this? Is there some option I can use to have npm forgo checking for depdendencies and just install my module locally without any other checks? -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Build error while installing nodemailer on Win 7
This is actually not an error but a warning (see npm WARN). On Windows one optional dependency can't be compiled but it doesn't matter much, the module should still work fine. On Sep 12, 12:50 pm, Thomas White thomas.0...@gmail.com wrote: Dear group, I have the following build error while installing nodemailer on Win 7. Any ideas? Thomas -- C:\Users\twhitenpm -g install nodemailer npm http GEThttp://registry.npmjs.org/nodemailer npm http 304http://registry.npmjs.org/nodemailer npm http GEThttp://registry.npmjs.org/mailcomposer npm http GEThttp://registry.npmjs.org/simplesmtp npm http GEThttp://registry.npmjs.org/optimist npm http 304http://registry.npmjs.org/simplesmtp npm http 304http://registry.npmjs.org/mailcomposer npm http 304http://registry.npmjs.org/optimist npm http GEThttp://registry.npmjs.org/xoauth2 npm http GEThttp://registry.npmjs.org/rai npm http GEThttp://registry.npmjs.org/mimelib npm http GEThttp://registry.npmjs.org/wordwrap npm http 304http://registry.npmjs.org/rai npm http 304http://registry.npmjs.org/xoauth2 npm http GEThttp://registry.npmjs.org/request npm http 304http://registry.npmjs.org/mimelib npm http 304http://registry.npmjs.org/wordwrap npm http 304http://registry.npmjs.org/request npm http GEThttp://registry.npmjs.org/addressparser npm http GEThttp://registry.npmjs.org/encoding npm http 304http://registry.npmjs.org/addressparser npm http 304http://registry.npmjs.org/encoding npm http GEThttp://registry.npmjs.org/iconv-lite npm http GEThttp://registry.npmjs.org/iconv npm http 304http://registry.npmjs.org/iconv npm http 304http://registry.npmjs.org/iconv-lite ic...@1.2.3 install C:\Users\twhite\AppData\Roaming\npm\node_modules\nodemailer\node_modules\ma ilcomposer\node_modules \mimelib\node_modules\encoding\node_modules\iconv node-gyp rebuild C:\Users\twhite\AppData\Roaming\npm\node_modules\nodemailer\node_modules\ma ilcomposer\node_modules\mimelib\node_modules\encoding\node_modules\iconvno de C:\Program Files x86)\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\ bin\node-gyp.js rebuild Building the projects in this solution one at a time. To enable parallel build, please add the /m switch. C:\Users\twhite\AppData\Roaming\npm\node_modules\nodemailer\node_modules\ma ilcomposer\node_modules\mimelib\node_modules \encoding\node_modules\iconv\build\iconv.vcxproj(18,3): error MSB4019: The imported project C:\Microsoft.Cpp.Default.props was not found. Confirm that the path in the Import declaration is correct, and that the file exists on disk. gyp ERR! build error gyp ERR! stack Error: `C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe` failed with exit code: 1 gyp ERR! stack at ChildProcess.onExit (C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:219:23) gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:91:17) gyp ERR! stack at Process._handle.onexit (child_process.js:678:10) gyp ERR! System Windows_NT 6.1.7601 gyp ERR! command node C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js rebuild gyp ERR! cwd C:\Users\twhite\AppData\Roaming\npm\node_modules\nodemailer\node_modules\ma ilcomposer\node_modules\mimelib\node_modules\encoding\node_modules\iconv gyp ERR! node -v v0.8.9 gyp ERR! node-gyp -v v0.6.8 gyp ERR! not ok npm WARN optional dep failed, continuing ic...@1.2.3 C:\Users\twhite\AppData\Roaming\npm\nodemailer - C:\Users\twhite\AppData\Roaming\npm\node_modules\nodemailer\bin\nodema iler nodemai...@0.3.27C:\Users\twhite\AppData\Roaming\npm\node_modules\nodemailer ├── optim...@0.3.4 (wordw...@0.0.2) ├── simples...@0.1.24 (r...@0.1.6, xoau...@0.1.1) └── mailcompo...@0.1.19 (mime...@0.2.4) -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Memory leak, growing RSS and debugging
Nothing new, even with node 0.8.8. However it does not feel like a leak (where RSS grows until the process crashes), it just fills most of the system memory and then stays at this level (even when all the connections are closed). I suspect V8 memory management to be the culprit. Nico Am 12.09.2012 um 02:58 schrieb wavded wav...@gmail.com: Nico did you have any luck in your debugging adventures? My symptoms seems to very closely match yours. Was going to try mtrace. On Monday, March 19, 2012 11:52:34 AM UTC-5, Nico Kaiser wrote: Thanks Ilya, I'll have a second look at node-mtrace. I tried this (as I did read the list ;-)), but it did not help much, and I hoped someone could identify a specific class of problems with my description (RSS grows, heap stays ok)... Nico Am Montag, 19. März 2012 16:06:38 UTC+1 schrieb Ilya Dmitrichenko: On 19 March 2012 14:09, Nico Kaiser ni...@kaiser.me wrote: How can I debug this behavior? I tried node-inspector, but v8-profiler only works with Node 0.4. Running node-gc every few seconds smoothes the memory curve, but does not help anything. If you did read the list, you would come across the same issue being discussed in this post: https://groups.google.com/d/msg/nodejs/Aq9BId5Tff8/7G3JxaIVd2YJ https://github.com/Jimbly/node-mtrace I observed that process.memoryUsage().heapTotal stays at an acceptable level (about 150 MB), only rss grows until the process gets killed. Does this tell anything, e.g. Buffer leak? (I know the WebSocket modules use lots of small buffers, but they should get freed, shouldn't they?). Do you have any hint where I can look for leaks? Thanks, Nico -- 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 group, send email to nod...@googlegroups.com To unsubscribe from this group, send email to nodejs+un...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Memory leak, growing RSS and debugging
Am 13.09.2012 um 10:05 schrieb Stefan Zehe s.z...@upjers.com: i solved my problems with an update to 0.8.9. in 0.8.3 there was a bugfix events: Fix memory leak from removeAllListeners (Nathan Rajlich) which might caused a steady growing _events-array. I'll check if I can get information about the _events arrays, but as I wrote before, 0.8.8 did not change much: http://cl.ly/image/2Y3N3w0t1I34 Nico -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Anonymous functions garbage collection
On 13/09/2012, at 08:00, Maxim Kazantsev wrote:
It is a pretty typical approach to use an anonymous function for asynchronous
calls from inside a loop:
var a = getInitialData();
for (var i = 0, len = a.length; i len; i++) {
(function(el) {
/* do something non-blocking here */
})(a[i]);
}
JSLint doesn't like this code with Don't make functions within a loop
warning, and it is actually right since it really creates a new anonymous
function on every single loop iteration. An obvious solution is to declare
this function outside a loop, but it would make a code less readable.
Come on!
Even if a declaration would just precede the loop: you see a call here, you
see a declaration somewhere else, and here you are, lost all your attention.
Perhaps. Or perhaps not. If you give the inner function a good name it will
help understand what's going on there.
My question is how bad this approach is for an overall performance?
Well, even though this:
function ƒ (i) { ctr+= i }
while (i--) ƒ(i);
is twice as fast as this:
while (i--) (function (i) { ctr+= i })(i);
https://gist.github.com/3714498
$ node test.js
(function (i) { ctr+= i })(i) - 39.74ns
ƒ(i) - 18.99ns
the difference is tiny, only 20 nano seconds!
In particular, how fast and efficient a garbage collection of anonymous
functions is? How much memory a typical anonymous function can consume and
how long it may exist in a memory?
I wouldn't bother too much about these things either. Simply follow Crock's
advice and declare ƒ outside of the loop. Or don't, it should just work in any
case.
--
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 group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Giving up on node.js / Flatiron / hook.io
I have no idea who you are Nathan. We've never worked on anything together before and we don't know each other. I'm not sure why you feel compelled to join this conversation and make judgements. On Thu, Sep 13, 2012 at 5:13 AM, Nathan White changereal...@gmail.comwrote: Marak, For the record I think your a pretty cool guy I just don't agree with your actions. You have let your ego distort the lens of reality. I, like yourself am very much a risk taker. With risks there are successes and failures. Look forward not backwards. It is admiral to inform the community about your changing involvement on projects. This has been the guise of this thread but not the true motive. People have asked if you will transfer ownership, with no response. There is a reason github made this a core feature. We all thank you for your involvement and wish you the best of luck in your future endeavors. Visions, strategies and goals change at companies all the time, especially startups. It is obvious that your not in alignment with your previous employer. Remember there are many other people involved in building companies. Teams need unity not discord. Companies must remove barriers to unity, sometimes it people. It's not about who is right or wrong, it just is. Move on. Put your talents to use, you should have no problem finding a paycheck. The self loathing will get you nowhere. On Sep 13, 2012, at 12:03 AM, Marak Squires marak.squi...@gmail.com wrote: Nathan - My intention was to inform the community I would no longer be maintaining a lot of projects that many developers communicate with me about on a semi-frequent basis. The alternative would have been to silently stop supporting these projects ( disappear ) without any notice or explanation. - Marak On Wed, Sep 12, 2012 at 10:17 PM, Nathan White changereal...@gmail.comwrote: I usually refrain from this bs but when people start asking for explanations about such absurdities I find it very hard to refrain. Marak's behavior is childish and deserves no explaination. The way he brought this shit to the forum should signal why he was fired. None of these issues should take away from all the other talented members of nodejitsu. It doesn't matter if Marak is right, to handle an issue like this in a public forum is inexcusable. On Sep 12, 2012, at 10:33 PM, Adam Crabtree atcrabt...@gmail.com wrote: When a leader departs from a community like this, a reasonable explanation helps answer the most basic questions that are on everyone's minds, while setting expectations of privacy in what they chose not to share. We should respect that and appreciate Marak's willingness to share personal details for the sake of greater clarity. Dramatic or not, none of us knows unless we know the whole story, which Marak chose not to share. Consider reaching out to Marak privately to encourage him in what is obviously a less than ideal situation. Otherwise, let's do as Mikeal suggests. Cheers, Adam Crabtree On Wed, Sep 12, 2012 at 12:46 PM, Micheil Smith mich...@brandedcode.comwrote: Really, that was just me getting a wee bit annoyed at the idea of the whole dramatisation here. If a company fires you, they either had a reason to, or, you have a lawsuit you can probably press, if you really want to. No need to make a big noise about it and try to paint them out as evil or wrong or whatever, it's fine though if someone asks that you're honest about it, but do we really need to discussion or even here about Marak's firing on the Node.js mailing list? As far as I'm concerned, not really, no. – Micheil On 12/09/2012, at 6:43 PM, Mikeal Rogers wrote: It is beyond foolish to speculate about why someone was fired from an announcement like this. I suggest you ask Marak or someone else at nodejitsu you know personally why this happened if you find it necessary to gossip. -Mikeal On Sep 12, 2012, at September 12, 201210:41 AM, Micheil Smith mich...@brandedcode.com wrote: Wasn't wanting to add into this, but reading between the lines it reads as if there was a conflict of interest, Marak was developing something open-source that was seen as a potential competitor to the closed-source product he was being paid to work on. Which, if he wished to not stop work on that potential competitor, then sure, sounds fine to dismiss him from the position he held at the company. And then, all that aside, I can understand being angry at a company, but the tone of that email was way off. Sure, if people ask you directly as to why, you can say something to them about it, but no need to make a massive show out of it. – Micheil On 12/09/2012, at 4:54 PM, Jeff Barczewski wrote: Yes, it would be beneficial for both sides to communicate a summary of what transpired to get to this point, rather than leaving this nebulous cloud over everything. Marak, have you looked into those
[nodejs] Re: `npm install -g .`, but faster...
If you're running test on the install process itself, running `npm install` inside the package directory should do it without reinstalling every dependency. If you want to test that the package works correctly when called from the cli, you can run `npm link`. That will create a symlink that will always point to the latest version. On Thursday, September 13, 2012 7:37:35 AM UTC-7, Tony Lukasavage wrote: I have a node project I'm working on that I frequently install with `npm install -g .` before running tests and such against the installed executable. When I do this, there's always a few seconds of waiting for npm to establish dependencies and do whatever else it does under the hood. I was wondering if there was a faster way to do this? Is there some option I can use to have npm forgo checking for depdendencies and just install my module locally without any other checks? -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Giving up on node.js / Flatiron / hook.io
http://www.youtube.com/watch?feature=player_detailpagev=xJjCnWm5cvE#t=100s On Wednesday, September 12, 2012 2:28:22 PM UTC-5, Tim Dickinson wrote: Get a job! On Wednesday, September 12, 2012 6:17:48 AM UTC-4, Filipe wrote: Tim, when you already have food on the table, right? -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Giving up on node.js / Flatiron / hook.io
I'm just a newbie here, don't know anyone. But perhaps people who contributed substantially to the project deserve a bit of respect in general, more so if they're bright and talented. (I'm not, wish I were). Not some of the comments when things go wrong. Companies have no heart and are not supposed to have one by definition, stuff like this happens when agendas clash. And Open Source can be double edged sometimes? Wish you best of luck, set out on your own, in a year you laugh about the whole thing. Tested! On 13/09/12 17:57, Marak Squires wrote: I have no idea who you are Nathan. We've never worked on anything together before and we don't know each other. I'm not sure why you feel compelled to join this conversation and make judgements. On Thu, Sep 13, 2012 at 5:13 AM, Nathan White changereal...@gmail.com wrote: Marak, For the record I think your a pretty cool guy I just don't agree with your actions. You have let your ego distort the lens of reality. I, like yourself am very much a risk taker. With risks there are successes and failures. Look forward not backwards. It is admiral to inform the community about your changing involvement on projects. This has been the guise of this thread but not the true motive. People have asked if you will transfer ownership, with no response. There is a reason github made this a core feature. We all thank you for your involvement and wish you the best of luck in your future endeavors. Visions, strategies and goals change at companies all the time, especially startups. It is obvious that your not in alignment with your previous employer. Remember there are many other people involved in building companies. Teams need unity not discord. Companies must remove barriers to unity, sometimes it people. It's not about who is right or wrong, it just is. Move on. Put your talents to use, you should have no problem finding a paycheck. The self loathing will get you nowhere. On Sep 13, 2012, at 12:03 AM, Marak Squires marak.squi...@gmail.com wrote: Nathan - My intention was to inform the community I would no longer be maintaining a lot of projects that many developers communicate with me about on a semi-frequent basis. The alternative would have been to silently stop supporting these projects ( disappear ) without any notice or explanation. - Marak On Wed, Sep 12, 2012 at 10:17 PM, Nathan White changereal...@gmail.com wrote: I usually refrain from this bs but when people start asking for explanations about such absurdities I find it very hard to refrain. Marak's behavior is childish and deserves no explaination. The way he brought this shit to the forum should signal why he was fired. None
Re: [nodejs] Re: Giving up on node.js / Flatiron / hook.io
I don't think Marak was attempting to do anything other than inform the community he was stepping down. It got emotional, sure, but you can't blame him for that. Sometimes its hard to contain your emotion in these situations, because you have a lot invested in it. Sometimes, your entire body and soul. I think we all know MS had a lot invested in this. I don't think you should be criticizing people for that, for not being automata in always in service of corporations and business - first and foremost because this is an open source community which contains enthusiasts and freelancers as well. I also don't think that, when someone has just recently been let go, that you should be ex I *certainly* don't think you should be saying something along the lines should signal why someone was fired. Really? *Wow*. In situations like this, startups always have the option to get out in front of the situation and announce that a major member is leaving. This has happened at every single start up I have worked for. They should have done that, and they didn't. The reason why they should do it is precisely this, to avoid having to have the person severed explain - potentially emotionally - to the rest of the community why they will no longer be participating in projects that are beyond the scope of a company's NDA. This is what happens when they don't. I respect everyone over there at NJ, but that was a misstep. If you have scathing words, keep them to yourself. The only thing you did was damage the espirit de corps of this community. On Thu, Sep 13, 2012 at 8:13 AM, Nathan White changereal...@gmail.comwrote: Marak, For the record I think your a pretty cool guy I just don't agree with your actions. You have let your ego distort the lens of reality. I, like yourself am very much a risk taker. With risks there are successes and failures. Look forward not backwards. It is admiral to inform the community about your changing involvement on projects. This has been the guise of this thread but not the true motive. People have asked if you will transfer ownership, with no response. There is a reason github made this a core feature. We all thank you for your involvement and wish you the best of luck in your future endeavors. Visions, strategies and goals change at companies all the time, especially startups. It is obvious that your not in alignment with your previous employer. Remember there are many other people involved in building companies. Teams need unity not discord. Companies must remove barriers to unity, sometimes it people. It's not about who is right or wrong, it just is. Move on. Put your talents to use, you should have no problem finding a paycheck. The self loathing will get you nowhere. On Sep 13, 2012, at 12:03 AM, Marak Squires marak.squi...@gmail.com wrote: Nathan - My intention was to inform the community I would no longer be maintaining a lot of projects that many developers communicate with me about on a semi-frequent basis. The alternative would have been to silently stop supporting these projects ( disappear ) without any notice or explanation. - Marak On Wed, Sep 12, 2012 at 10:17 PM, Nathan White changereal...@gmail.comwrote: I usually refrain from this bs but when people start asking for explanations about such absurdities I find it very hard to refrain. Marak's behavior is childish and deserves no explaination. The way he brought this shit to the forum should signal why he was fired. None of these issues should take away from all the other talented members of nodejitsu. It doesn't matter if Marak is right, to handle an issue like this in a public forum is inexcusable. On Sep 12, 2012, at 10:33 PM, Adam Crabtree atcrabt...@gmail.com wrote: When a leader departs from a community like this, a reasonable explanation helps answer the most basic questions that are on everyone's minds, while setting expectations of privacy in what they chose not to share. We should respect that and appreciate Marak's willingness to share personal details for the sake of greater clarity. Dramatic or not, none of us knows unless we know the whole story, which Marak chose not to share. Consider reaching out to Marak privately to encourage him in what is obviously a less than ideal situation. Otherwise, let's do as Mikeal suggests. Cheers, Adam Crabtree On Wed, Sep 12, 2012 at 12:46 PM, Micheil Smith mich...@brandedcode.comwrote: Really, that was just me getting a wee bit annoyed at the idea of the whole dramatisation here. If a company fires you, they either had a reason to, or, you have a lawsuit you can probably press, if you really want to. No need to make a big noise about it and try to paint them out as evil or wrong or whatever, it's fine though if someone asks that you're honest about it, but do we really need to discussion or even here about Marak's firing on the Node.js mailing list? As far as I'm concerned, not really, no.
Re: [nodejs] Re: Giving up on node.js / Flatiron / hook.io
*explaining why someone was potentially let go when you don't know the situation yourself. On Thu, Sep 13, 2012 at 1:01 PM, Stewart Mckinney lordma...@gmail.comwrote: I don't think Marak was attempting to do anything other than inform the community he was stepping down. It got emotional, sure, but you can't blame him for that. Sometimes its hard to contain your emotion in these situations, because you have a lot invested in it. Sometimes, your entire body and soul. I think we all know MS had a lot invested in this. I don't think you should be criticizing people for that, for not being automata in always in service of corporations and business - first and foremost because this is an open source community which contains enthusiasts and freelancers as well. I also don't think that, when someone has just recently been let go, that you should be ex I *certainly* don't think you should be saying something along the lines should signal why someone was fired. Really? *Wow*. In situations like this, startups always have the option to get out in front of the situation and announce that a major member is leaving. This has happened at every single start up I have worked for. They should have done that, and they didn't. The reason why they should do it is precisely this, to avoid having to have the person severed explain - potentially emotionally - to the rest of the community why they will no longer be participating in projects that are beyond the scope of a company's NDA. This is what happens when they don't. I respect everyone over there at NJ, but that was a misstep. If you have scathing words, keep them to yourself. The only thing you did was damage the espirit de corps of this community. On Thu, Sep 13, 2012 at 8:13 AM, Nathan White changereal...@gmail.comwrote: Marak, For the record I think your a pretty cool guy I just don't agree with your actions. You have let your ego distort the lens of reality. I, like yourself am very much a risk taker. With risks there are successes and failures. Look forward not backwards. It is admiral to inform the community about your changing involvement on projects. This has been the guise of this thread but not the true motive. People have asked if you will transfer ownership, with no response. There is a reason github made this a core feature. We all thank you for your involvement and wish you the best of luck in your future endeavors. Visions, strategies and goals change at companies all the time, especially startups. It is obvious that your not in alignment with your previous employer. Remember there are many other people involved in building companies. Teams need unity not discord. Companies must remove barriers to unity, sometimes it people. It's not about who is right or wrong, it just is. Move on. Put your talents to use, you should have no problem finding a paycheck. The self loathing will get you nowhere. On Sep 13, 2012, at 12:03 AM, Marak Squires marak.squi...@gmail.com wrote: Nathan - My intention was to inform the community I would no longer be maintaining a lot of projects that many developers communicate with me about on a semi-frequent basis. The alternative would have been to silently stop supporting these projects ( disappear ) without any notice or explanation. - Marak On Wed, Sep 12, 2012 at 10:17 PM, Nathan White changereal...@gmail.comwrote: I usually refrain from this bs but when people start asking for explanations about such absurdities I find it very hard to refrain. Marak's behavior is childish and deserves no explaination. The way he brought this shit to the forum should signal why he was fired. None of these issues should take away from all the other talented members of nodejitsu. It doesn't matter if Marak is right, to handle an issue like this in a public forum is inexcusable. On Sep 12, 2012, at 10:33 PM, Adam Crabtree atcrabt...@gmail.com wrote: When a leader departs from a community like this, a reasonable explanation helps answer the most basic questions that are on everyone's minds, while setting expectations of privacy in what they chose not to share. We should respect that and appreciate Marak's willingness to share personal details for the sake of greater clarity. Dramatic or not, none of us knows unless we know the whole story, which Marak chose not to share. Consider reaching out to Marak privately to encourage him in what is obviously a less than ideal situation. Otherwise, let's do as Mikeal suggests. Cheers, Adam Crabtree On Wed, Sep 12, 2012 at 12:46 PM, Micheil Smith mich...@brandedcode.com wrote: Really, that was just me getting a wee bit annoyed at the idea of the whole dramatisation here. If a company fires you, they either had a reason to, or, you have a lawsuit you can probably press, if you really want to. No need to make a big noise about it and try to paint them out as evil or wrong or whatever, it's fine
Re: [nodejs] Anonymous functions garbage collection
Take advantage of function hoisting and make the code more readable:
var a = getInitialData(), I, len;
for (i=0, len=a.length; ilen; i++) {
doSomething(a[i]);
}
function doSomething(el){
}
--
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 group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Giving up on node.js / Flatiron / hook.io
On Wed, Sep 12, 2012 at 11:17:00PM -0600, Nathan White wrote: I usually refrain from this bs but when people start asking for explanations about such absurdities I find it very hard to refrain. Marak's behavior is childish and deserves no explaination. The way he brought this shit to the forum should signal why he was fired. None of these issues should take away from all the other talented members of nodejitsu. It doesn't matter if Marak is right, to handle an issue like this in a public forum is inexcusable. What is inexcusable? Announcing that you're no longer able to maintain open source software that you've created? Telling your Internet friends you've been fired? Letting people know something of the hurt you feel that the work you've focused on has come to an end for you? What's inexcusable exactly? I've known people who couldn't have been happier with their termination. It's the end of a relationship. In our industry, quit whether someone is fired or whether they quit is about as meaningful as who dumped who first. I believe our compatriot is taking his dismissal pretty hard, but it doesn't make sense to me. I don't believe he has to take it that hard. I want to see him rebound. I want to see him fork and carry on. Getting fired is something that happens to a person. It's part of that person's story. They get to tell their story. He is part of the community. His circumstance effects the community. He gets to talk about it. He is allowed to tell people that this circumstance makes him sad. It makes me sad. I don't understand your vindictiveness. It's really off putting. Reads like a craven display of deference to authority to me. -- Alan Gutierrez - @bigeasy -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Giving up on node.js / Flatiron / hook.io
Everyone, Please stop. Marak's relationship with Nodejitsu is between Marak and Nodejitsu. He'll got plenty of ability to get another job when and if he decides to. He did the responsible thing by letting people know that he's not going to be maintaining some projects. None of us have enough information to speculate about why or how things turned out the way they did, and we can only make the drama worse by doing so. The best thing to do is to leave it alone. On Thu, Sep 13, 2012 at 11:27 AM, Alan Gutierrez a...@prettyrobots.com wrote: On Wed, Sep 12, 2012 at 11:17:00PM -0600, Nathan White wrote: I usually refrain from this bs but when people start asking for explanations about such absurdities I find it very hard to refrain. Marak's behavior is childish and deserves no explaination. The way he brought this shit to the forum should signal why he was fired. None of these issues should take away from all the other talented members of nodejitsu. It doesn't matter if Marak is right, to handle an issue like this in a public forum is inexcusable. What is inexcusable? Announcing that you're no longer able to maintain open source software that you've created? Telling your Internet friends you've been fired? Letting people know something of the hurt you feel that the work you've focused on has come to an end for you? What's inexcusable exactly? I've known people who couldn't have been happier with their termination. It's the end of a relationship. In our industry, quit whether someone is fired or whether they quit is about as meaningful as who dumped who first. I believe our compatriot is taking his dismissal pretty hard, but it doesn't make sense to me. I don't believe he has to take it that hard. I want to see him rebound. I want to see him fork and carry on. Getting fired is something that happens to a person. It's part of that person's story. They get to tell their story. He is part of the community. His circumstance effects the community. He gets to talk about it. He is allowed to tell people that this circumstance makes him sad. It makes me sad. I don't understand your vindictiveness. It's really off putting. Reads like a craven display of deference to authority to me. -- Alan Gutierrez - @bigeasy -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Stream to multi-stream
Hey all. I'm looking for a module that would allow me to have one net socket or other stream and layer other streams on top of it. I was thinking of writing my own module for this but if anyone knows of something like this then i would look at it first before i write my own. -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Redirection service for the Node.js community
Hi everyone, I made a little redirect service for myself (usually just to redirect www-non-www or the other way around) and thought it could be useful for everyone. It's on Nodejitsu - which I thank them for - so give me a pull request [1] with your domain info and I'll get your redirects up usually within a day or so (I'll batch them to save myself some time). Instructions on the site: * http://redirects.jit.su/ * https://github.com/appsattic/redirects Thanks to Nodejitsu for the service and for confirming to me that I can map as many domains as I like to the same application. Hope the service can be useful for you. Cheers, Andy [1] Has to be a pull request since the domain will need to be in the config file when deployed. Read the site for more details. -- Andrew Chilton e: chi...@appsattic.com w: http://appsattic.com/ t: https://twitter.com/andychilton -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Stream to multi-stream
Do you mean pipe on stream to several streams? On Thursday, September 13, 2012 12:33:04 PM UTC-7, Tim Dickinson wrote: Hey all. I'm looking for a module that would allow me to have one net socket or other stream and layer other streams on top of it. I was thinking of writing my own module for this but if anyone knows of something like this then i would look at it first before i write my own. -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Stream to multi-stream
Do you mean pipe on stream to several streams? No what I mean is to have one stream and and then have other stream pipe to it. So mulit point to mulit point on one stream. -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Stream to multi-stream
https://github.com/dominictarr/mux-demux On Thu, Sep 13, 2012 at 1:14 PM, Tim Dickinson price.ti...@gmail.comwrote: Do you mean pipe on stream to several streams? No what I mean is to have one stream and and then have other stream pipe to it. So mulit point to mulit point on one stream. -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: node.js fuse bindings?
Hi everyone, I just published these Fuse bindings for node.js 0.8.x: https://github.com/bcle/fuse4js I developed it for an internal project at my company. Feel free to give it a try and give me feedback. Bich C. Le VMware, Inc. -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] npm got Segmentation fault at linux (npm 1.1.48 node v0.8.6)
hi, found this works: /usr/lib/nodejs/npm/bin/npm-cli.js list but* npm list* still segement fault 在 2012年8月20日星期一UTC+8下午10时48分46秒，Ben Noordhuis写道： On Fri, Aug 17, 2012 at 5:30 PM, TZ (天猪) ati...@qq.com javascript: wrote: https://www.dropbox.com/s/vgcgatk917fovmb/core.7355 https://www.dropbox.com/s/9oa3li8inq6wzx2/node Thanks. I looked at it but couldn't find the culprit - there's a uv_async_t handle that seems mostly uninitialized (most fields are 0 or NULL) for no apparent reason. -- 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 group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
