Seems to me like there's very little new here to anyone paying attention to the space. They didn't raise any limits - they just fixed their own badly written co

Seems to me like there's very little new here to anyone paying attention to the space. They didn't raise any limits - they just fixed their own badly written code. The 1.5 gig limit is not widely known (it's a limit of V8 and I believe, correct me if I'm wrong here, that it's improved in later versions due to some changes to GC) but if you're hitting it you're doing something massively wrong: like they were here. Splitting data up into chunks for the event loop to process is priority one in any Node app that deals with data processing. It has been for a long time. This is true anywhere you run JavaScript. It's where libraries like [Highland](http://highlandjs.org/ http://highlandjs.org/) excel and why Node has the concept of Buffers. Chunking data should be a no brainer and it's frankly a little strange that Jut weren't doing this in the first place. Raises questions about what else is not being done correctly under the hood. There's no meat here (aside from learning that NPM uses them).