Re: [nodejs] i2c-bus - A new I2C module for NodeBots

node forming. But apologies for the downer- writing in to say, thanks for the contribution! Glad to see this nice looking lib. -@rektide -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.co

[nodejs] streams2 polyfill/shim for browser

howdy node'ers- i've spotted deoxxa's streams2 shim, but it's built upon streams1. slightly OT, but is anyone aware of a streams2 polyfill/shim that works on the browser directly? kudos, -r -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailin

Re: [nodejs] Wanted: federated-event/message-emitting platform?

systems, but it's not, so use web standards to create and data-flow across collections. -rektide -- -- 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 Googl

Re: [nodejs] Trivial stream.Transform Attempt

That was super fun! I'd neglected to call stream.Transform's constructor when I derived from it. Everything appears to be working fine now, I think. The nop branch reflects this change. Thanks, & please pardon the interruption. O Mon, Feb 11, 2013 at 12:52:37AM -0500, rektide

[nodejs] Trivial stream.Transform Attempt

Hello hello lovely Node-js people- I'm trying to implement a very simple stream.Transform, but I appear to be doing something wrong! Please help me figure out how to get going with stream.Transform! My utterly trivial sample code is at- https://github.com/rektide/arclamp2/blob/no

Re: [nodejs] New GContext module, Integration between uv and GLib

Nicely done! Hopefully this work can be integrated with node-gir, which requires the user to execute the gst.main() loop the themselves (#2 on their "Things which dont work"). https://github.com/piotras/node-gir On Sat, Dec 15, 2012 at 05:47:05PM +0800, Fred Chien wrote: >Hi All, >I've

Re: [nodejs] Server-to-Server Communication

) and too high level (plenty of targets, let's call out hook.io randomly), creating MessageChannels and MessagePorts is to me a great middle-level of messaging abstraction, and it's one we'll continue to see more of in places outside of Node-land. -rektide -- Job Board: http://

Re: [nodejs] Dynamic content scrape with Node.js

sed. Good luck: https://github.com/chriso/node.io -rektide On Sat, Oct 06, 2012 at 01:34:03PM -0700, Narek Musakhanyan wrote: >Hey guys . I tried to scrape a data from a website using PHP cURL lib but >I failed  since cURl allows you to scrape only static content . But the >conte

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

> > ps. I'm really a nice guy, hopefully we can meet in person some day and > we'll laugh about this. Me too. I interpretted some subset of the conversation here as your intended target of shit-talking dogpile people, which didn't seem fair to me. Since you've disavowed that connection, attri

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

On Wednesday, September 19, 2012 8:55:00 PM UTC-4, Isaac Schlueter wrote: > > > No, Isaac. I feel pissed on here. Ack that. > > Ack'ed. > > Your original request for threads-in-node has been met with > explanations from me, Ben, and Paddybyers about what would need to be > done to make that ha

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

I gently suggest that if we'd found and settled on some technical topics, rather than meta-moderation, there would be six or seven posts here. If you feel topics not to your interest, I revert to my former stance which is: don't read them. This is a mailing list: 8/10 topics have no interest to

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

On Wednesday, September 19, 2012 6:30:07 PM UTC-4, Mikeal Rogers wrote: > > On Sep 19, 2012, at September 19, 20123:21 PM, rektide < > rek...@voodoowarez.com > wrote: > > > >> > I humbly propose not participating in things which annoy you or you >> find

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

> > > Isaac: I fully confess to being an ignorant childish distracting > useless retrogressive drag on the community, and I'm sorry if this > discussion in fact hurts us. Also, seek trained medical professional help. > These comments are trollish and inappropriate. No, Isaac. I feel pis

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

> Yes they do. I'm following this through the Google web UI. The two > discussions are interleaved in a single list and I did not pay attention to > the titles. Maybe Google does not like threads either :-) > Sorry! I see the same WTF'itude: I meant to cleanly fork & provide some consistency

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

> I wasn't really addressing you—your comments were entirely reasonable. I > was addressing the shit-talking dog-pile. > I challenge you to find anything in this thread that directly shit-talks Node or Joyent. I *want* to believe this is fair and balanced discussion. Jorge got a little tweake

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

> Multi-threading, even without zero copy, would allow for faster context > switching as well. Context switching is bad, process-per-thread is good and > helps avoids context switching, but there is a gain even if there is not an > easy zero copy benefit to be had. > *facepalm* s/process-per-

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

> I hate TAGG because it's built around the lie > that > zero-copy data sharing would be at all possible. V8 just isn't built to do > it, and making it so would be a monumental task. Google may be able to pull > it off it they c

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

ormed, and hope this community is civil and mature enough to help explore the topic with me. Respect, -rektide On Monday, September 17, 2012 6:09:32 PM UTC-4, Isaac Schlueter wrote: > > Everybody, > > These debates give me hives. Seriously, they make my skin crawl. > >

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

On Tuesday, September 18, 2012 1:26:13 PM UTC-4, Rick Waldron wrote: > > This morning I had a chance to ask Doug, in person, to clarify what he > meant by his statements about forking Node—as it turns out, his motivations > aren't sinister, nor are they really outrageous. > > Historically, Yaho

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

WebMessaging for life, and as usual, haters gonna hate. Stay positive kids. On Tuesday, September 18, 2012 1:31:41 PM UTC-4, Rick Waldron wrote: > > Almost forgot... > > When I mentioned threads, he scoffed and said "threads have no place in > JavaScript or Node". > > And there you have it, the

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

> > and is a huge annoyance and distraction for everyone who would like to > move forward I humbly propose not participating in things which annoy you or you find overly distracting. Everyone who feels capable of engaging in progressive dialectic engagement on technical topics and knows how

[nodejs] Re: Threading, and Dogmatisms.

Thanks so much for the informative reply: that's a lot of things I don't know about! On Sunday, September 16, 2012 6:22:50 PM UTC-4, Bradley Meck wrote: > > There are long discussions in the Node community about what happened when > we did try to use Isolates. The lack of thread level protectio

[nodejs] Threading, and Dogmatisms.

embrace input liberally. 4. Doing threads, safe concurrency right is what makes Rust so attractive, and Node can do it safely, cleanly too and nearly did, in the "isolates" branch. https://github.com/joyent/node/tree/isolates Onwards: On Sat, Sep 15, 2012 at 11:32:56AM -0700, Mark

[nodejs] Re: Threading, and Dogmatisms.

Google is too smart for me. I wrote this reply as a new thread, and Google has attached it to the old one. Apologies, but I am about to repost it sans-excerpts. -r -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You

[nodejs] Threading, and Dogmatisms.

embrace input liberally. 4. Doing threads, safe concurrency right is what makes Rust so attractive, and Node can do it safely, cleanly too and nearly did, in the "isolates" branch. https://github.com/joyent/node/tree/isolates Onwards: On Sat, Sep 15, 2012 at 11:32:56AM -0700, Mark

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

On Sat, Sep 15, 2012 at 04:56:40PM +0200, Arnout Kazemier wrote: > "Pull request or it didn't happen" Hi: https://github.com/xk/node-threads-a-gogo , or preferrably some better isolated manner of multi-threading with Transferable objects. > On 15 sep. 2012, at 16:45, Jorge wrote: > > http://w

Re: [nodejs] Looking for a good xml parser in stream mode

On Thu, Aug 30, 2012 at 02:05:21PM +0800, jason.桂林 wrote: >A protocol using xml, socket stream >first time I recieve  >blabl >3rd time I recieve >aThen I should get a xml blabla , and left waiting for new coming data. >Any good module to do that? Still hoping someon

[nodejs] Re: Why `fs.exists` has signature `(exists)` instead of `(err, exists)` ?

I would really really appreciate it if Node were to consistently get behind err being the first param, even when it's nonsensical. Readline.question could stand being made from answer => void to err,answer => void as well. On Friday, August 17, 2012 6:57:18 PM UTC-4, Alexey Petrushin wrote: > >

Re: [nodejs] webinos app contest

ink everyone owes it to themself to check out some Webinos. Ok, way late for the nerdiest of nerdy meetups, our regular EVE Online meetup. Cya all later, -rektide PS: https://plus.google.com/113218107235105855584/posts is my G+. JS, Ubicomp, hardware, space, & writing at least as good/b

[nodejs] Where is the app.request() function from Connect's tests defined?

27;m expecting to find it somewhere in the main Conenct lib[2] but after having cruised through the couple files in there a couple of times, I still haven't found where this is defined. Can anyone help point me to what I'm missing please? Thanks! [1] https://github.com/rektide/connect/tree

Re: [nodejs] NodeConf SummerCamp

Oh boy I wish this was in the cards for me this year. Camping & node: the only downside is having to come back to the real world after. On Wed, Jul 25, 2012 at 09:58:37AM -0700, Mikeal Rogers wrote: > It's that time of year again :) > > We're returning to Walker Creek Ranch for another unconfere

Re: [nodejs] Fwd: [CTTE #614907] Resolution of node/nodejs conflict

Glorious! So say we all! `node` for all! On Thu, Jul 12, 2012 at 11:41:39PM +0200, Carl Fürstenberg wrote: > -- Forwarded message -- > From: Don Armstrong > Date: Thu, Jul 12, 2012 at 8:59 PM > Subject: [CTTE #614907] Resolution of node/nodejs conflict > To: debian-devel-annou...

Re: [nodejs] worker thread API for node?

I'd love to see this, but then, I was also hoping to see isolates, and was imaginging a perfect fusion of the two. I don't believe there's any plan for either. Background on isolates: https://groups.google.com/forum/?fromgroups#!msg/nodejs/zLzuo292hX0/F7gqfUiKi2sJ On Thu, Jul 12, 2012 at 01:35:4

[nodejs] remoteable events

Hi nodejs group, Any suggestions for drop-in enhancements/replacements to EventEmitter which allow events to replicate cross-process or across different systems? Bonus points for anything that supports multiple transports! -rektide -- Job Board: http://jobs.nodejs.org/ Posting guidelines

[nodejs] Re: Isolates removed

> but has ultimately turned out to cause too much instability in node's > internal functionality to justify continuing with it at this time. please specify, elaborate, explain or make note upon this conflict, as if in warning to those who would have wished to pursue the cause further. -- Job Bo