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

Alright guys, I believe we need to move on from this issue now. I don't see this getting anywhere and the last thing we want is to have non-technical discussions like these continue in a technical mailing list. Thanks guys! On Sat, Dec 7, 2013 at 11:23 AM, mgutz wrote: > So does Bryan still hav

[nodejs] Re: Ben Noordhuis's Departure

So does Bryan still have a job, since he was so quick to fire an "asshole" employee. On Tuesday, December 3, 2013 9:36:07 PM UTC-8, Isaac Schlueter wrote: > > As of this past weekend, Ben Noordhuis has decided to step away from > Node.js and libuv, and is no longer acting as a core committer. >

Re: [nodejs] Ben Noordhuis's Departure

Adam: From a job point of view Bryan is Isaac boss (I'm assuming?). Bryan was also the first sponsor of node and enabled Ryan in the early days. Also Bryan did defend Isaac in that post and honestly that was correct: Isaacs behavior was always correct and bare in mid that in this whole ordeal he wa

Re: [nodejs] node programming style question

 07.12.2013, 01:04, "Matt" :On Fri, Dec 6, 2013 at 4:01 PM, Alex Kocharin wrote:I'm still seeing Object. in stack traces from time to time though. Perhaps from: (function () { x() })(); ? Hmm... if you throw at the root of the module, it does show that. But it's a non-issue reall

Re: [nodejs] node programming style question

Personally, I declare all elements, functions as others, I name each function and I assign to a variable of the same name. Here's how I structure each scope : :// declaration block var foo; // allocation block foo = function foo() { var bar; // ... }; In this way, my declaration block

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

How about we start assuming that individuals are responsible for their own actions rather that shills for their current employer. Pretty much everyone we're talking about has a career and credibility extending much farther back than their current employment. -Mikeal On Dec 6, 2013, at 12:46PM,

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

On Fri, Dec 6, 2013 at 3:46 PM, Adam Crabtree wrote: > A leveled and rational response that ignores Bryan Cantrill shockingly > inflammatory public attempt at shaming Ben. The community response is > (mostly) based on public information, so if there is a private > justification for Bryan's public

Re: [nodejs] node programming style question

On Fri, Dec 6, 2013 at 4:01 PM, Alex Kocharin wrote: > I'm still seeing Object. in stack traces from time to time > though. > Perhaps from: (function () { x() })(); ? -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guideli

Re: [nodejs] node programming style question

 Hmm, sorry, you're right. v8 had improved these things apparently. I'm still seeing Object. in stack traces from time to time though.  07.12.2013, 00:44, "Matt" :On Fri, Dec 6, 2013 at 2:49 PM, Alex Kocharin wrote:It's bad because of stack traces. It is a big deal. Only in weird

Re: [nodejs] HTTP Server Concurrent Requests

Great advice, thanks Mikeal Adam > On 6 Dec 2013, at 16:30, Mikeal Rogers wrote: > > Back then we spent a good amount of time debating whether or not this > mattered. I remember that Ryan was particularly enamored with pipelining. > > What it really comes down to is that pipelineing is almos

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

@Isaac S A leveled and rational response that ignores Bryan Cantrill shockingly inflammatory public attempt at shaming Ben. The community response is (mostly) based on public information, so if there is a private justification for Bryan's publicly rude behavior and treatment of a community member

Re: [nodejs] node programming style question

On Fri, Dec 6, 2013 at 2:49 PM, Alex Kocharin wrote: > It's bad because of stack traces. It is a big deal. > Only in weird browsers. In node it is fine for stack traces: > var x = function () { throw new Error("in X") } > var y = function () { x() } > y(); Error: in X at x (repl:1:29)

Re: [nodejs] node programming style question

 It's bad because of stack traces. It is a big deal. I supported a patch for `var x = function x(){}` for coffeescript a while ago (https://github.com/jashkenas/coffee-script/issues/15#issuecomment-3771331). Later I just got tired of this and stopped using coffeescript completely, but the argument

Re: [nodejs] node programming style question

> You're not a bad person if you do `var x = function(){}`. That's good because everyone using coffeescript has to use this. :-) On Fri, Dec 6, 2013 at 8:51 AM, Isaac Schlueter wrote: > Named function is better, for hoisting, debugging, and recursion. > > ## hoisting > > It's hoisted as a fu

Re: [nodejs] Re: node.js needs a new home

 06.12.2013, 20:44, "Isaac Schlueter" :Alex, Alexey: Node's license is MIT.  It includes the licenses and copyright notices of its bundled dependencies, as is standard practice, and required for compliance with some of the dependencies' licenses.  (Even where not explicitly required, it's nice to g

Re: [nodejs] Re: node.js needs a new home

On Fri, Dec 6, 2013 at 2:02 PM, // ravi wrote: > Here’s one problem, the one that set this off: > > --- > If NodeJS is a *community*, it should not tolerate gendered language use > (in English; I am told the issue is more nuanced in languages like > Japanese, upon which I cannot comment). The

Re: [nodejs] Re: node.js needs a new home

On Dec 6, 2013, at 11:43 AM, Isaac Schlueter wrote: > > I am getting the sense that we're pitching solutions rather than exposing > problems. Let's get a solid bug report and reproduction test case before we > rearchitect anything. > > What *problems* are there today? Once we have some rough

Re: [nodejs] Re: node.js needs a new home

There are many profit-based entities behind Open Source projects that belong to foundations... the difference is those entities do not OWN anything related to the projects they are supporting. Which to me... is in the true spirit of Open Source. After spending several days reading through all the

Re: [nodejs] node programming style question

Named function is better, for hoisting, debugging, and recursion. ## hoisting It's hoisted as a function, not as "undefined". ``` console.log(typeof unnamed); console.log(typeof named); var unnamed = function (){}; function named() {} ``` ## debugging The stack traces generated in V8 once up

Re: [nodejs] Re: node.js needs a new home

Alex, Alexey: Node's license is MIT. It includes the licenses and copyright notices of its bundled dependencies, as is standard practice, and required for compliance with some of the dependencies' licenses. (Even where not explicitly required, it's nice to give credit for what we're using, and al

[nodejs] node programming style question

I see both style and trying to understand the differences... Debugging, logging, other plus or minus... Option one: var zero = function (n){ return n < 10 ? "0" + n : n; }; Option two: function zero (n){ return n < 10 ? "0" + n : n; }; What is the "recommended" style and why?

Re: [nodejs] HTTP Server Concurrent Requests

Back then we spent a good amount of time debating whether or not this mattered. I remember that Ryan was particularly enamored with pipelining. What it really comes down to is that pipelineing is almost never faster than a keep-alive pool. The reason is that the client has no idea how long each

[nodejs] Re: Ben Noordhuis's Departure

Perhaps against my better judgement, I want to try to clear up a few things. First of all, to characterize Ben's departure, or the whole recent drama, as being over pronoun usage, is a radical oversimplification. Every group has internal tensions, and ours is no different. It is normal and healt

Re: [nodejs] HTTP Server Concurrent Requests

Three years has gone by since this last email and I wondered if anything changed since? Can a node.js client pipeline http requests (on a single keep-alive socket) rather than make each one wait until the last one completes? Thanks in advance Adam On Aug 25, 2010, at 9:23 PM, Isaac Schlueter

[nodejs] Re: [ANN] Put a status bar in your modules

Yeah, I wonder if npm can use that one to display download progress. On Friday, December 6, 2013 5:53:34 PM UTC+4, Gagle wrote: > > https://github.com/gagle/node-status-bar > > It is implemented to provide a status bar to the tftp client I'm writing ( > https://github.com/gagle/node-ntftp) > > a

[nodejs] Re: Ben Noordhuis's Departure

Thank you Ben for your great contributions! We're sad this happened. 'nuff said -- -- 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" gr

[nodejs] [ANN] Put a status bar in your modules

https://github.com/gagle/node-status-bar It is implemented to provide a status bar to the tftp client I'm writing (https://github.com/gagle/node-ntftp) a-file 17.8 MiB 23.6M/s 00:13 [#···] 6% You just need to pipe a stream to it! -- -- Job Board: htt

[nodejs] Re: TFTP client and server

The get command is fully implemented and tested (not formally, yet). It supports the de-facto rollover and windowed mode, so it can download and upload any file at a good transfer speed (it needs to be benchmarked). The CLI shell (if it is installed globally) is also fully implemented. This is t

Re: [nodejs] Ben Noordhuis's Departure

Am Freitag, 6. Dezember 2013 13:16:35 UTC+1 schrieb Alex Kocharin: > > > > On Friday, December 6, 2013 12:48:06 PM UTC+4, greelgorke wrote: > >> >> Second desaster resulted from the overly heavy reactions on github and >> here of several ppl, who are ocnsidered to be community leaders due to >>

Re: [nodejs] Ben Noordhuis's Departure

On Friday, December 6, 2013 12:48:06 PM UTC+4, greelgorke wrote: > > Second desaster resulted from the overly heavy reactions on github and > here of several ppl, who are ocnsidered to be community leaders due to > their merits or vocal presence. > Who are you talking about? I don't see any h

[nodejs] When will Chrome Beta for Android fully support webRTC and HTML5

I've tested my web application on several android mobile devices (smartphone, tablets). None of it works. The test link is here: http://meldville.com/demo/broadcaster.php It streams audio and video data to here: http://meldville.com/demo/audience.php It just only works on Chrome Beta for deskt

[nodejs] Re: Sleek.js MVC updated with abunch of updates !

Sleek.js webpage, demo & Supports are up now. Sorry for the inconvenience caused. Ask your questions here .. On Monday, November 25, 2013 2:55:42 PM UTC+5:30, Robin Samuel wrote: > > Sleek.js MVC released version 1.68, with a bunch of updates. Our first > sleek.js

Re: [nodejs] Ben Noordhuis's Departure

i'm following this whole diskussion for few days now and the only thing i can think about it is: omg what have you done, node community!? This whole thing gone so crazy and so sad. First of all its a multiple communication fail. It's ok to reject a commit for thatever reasons it might have b