node-v0.x-archive

I was referring to node <0.1.30[1] which did have promises for a while. largely from jQuery deferred, which were ungood in a couple ways I don't remember. but also remarkably similar. I still largely think kris kowal building the "Q" promise library is what made promises interesting, what surfaced the idea that we might want to first-class our completeablea/futures. I know kris had some specific inspirations but I forget what. pains me somewhat to this day that promises ultimately became somewhat un-value like, that handlers don't get to see what it was resolving. all the chain/spawn discussion, the functional promise folk: they got rolled by those insisting we had to target only the lowest rings of the developership, and that allowing more potent systems was unacceptable. wish I could find those es-discusa threads, for the powerful sorro

first commit is from 2013 [0], first Node that had Array.isArray was 0.1.15 from 2009 [1], thus making is as Node module was pointless, but polyfill for browsers might have some sense. - [0] https://github.com/juliangruber/isarray/commit/c8601522e3136... - [1] https://github.com/nodejs/node-v0.x-archive/blob/v0.1.15/Cha...

Array.isArray has been implemented in 1.3.16 of V8 [0] which was used in node 0.1.15! [1] doubt that someone even is using that old node.js this to me looks like 3rd-party packages that were added very long ago and the code was never updated. - [0] https://chromium.googlesource.com/v8/v8/+/refs/tags/1.3.16 - [1] https://github.com/nodejs/node-v0.x-archive/blob/v0.1.15/Cha...

There are some important differences here between NodeJS and Ruby. NodeJS child processes are completely independent and created with spawn. https://github.com/nodejs/node-v0.x-archive/issues/2334 CRuby forks using fork() and Copy-on-Write shares memory from parent to child. JRuby doesn't have a GIL so you only need a single process. Same with TruffleRuby. With CRuby, you're much better to run a bigger container with multiple processes than one process per container. With either NodeJS or CRuby you're still better to run less containers on bigger hosts. Each host has to duplicate the host OS and container infrastructure. Each container of a real production app also duplicates a bunch of stuff despite Docker's best attempts at sharing.

I'm not sure that this experiment is meaningful. The point of a preload-fork process model à la Unicorn is that the `fork` syscall gives you copy-on-write[1] shared memory between the parent and the child, so you save a bunch of time because you get to use the same piece of memory, and you save a bunch of space because you get to use the same piece of memory. In those cases, disabling GC and killing workers made sense because you could start another one up literally instantly, with basically zero cost in time or space. `fork` in Node.js[2] isn't a real `fork` in the syscall sense. Node.js's `fork` is more-or-less a misnomer; it doesn't use the `fork` syscall at all. It basically starts up a completely new process, and opens an IPC pipe between the parent and the child. There's none of the CoW memory sharing that you get from the syscall `

NodeJS is a multi-threaded process. You can verify it with top or ps command. Async methods to decode JSON: https://github.com/nodejs/node-v0.x-archive/issues/7543

This is a really good question and a really good point. There used to be a list of companies that "use" Node in some capacity, which appears to be removed: https://github.com/nodejs/node-v0.x-archive/wiki/Projects,-A... The time spent learning and configuring Node seems to have more cons than pros, for most projects, in my own anecdotal experience. Things like Horizon (http://horizon.io/) are changing this for the better. And are doing a really good job of making Node accessible.

For years, this limitation made using npm on Windows miserable[0][1]. [0] https://github.com/nodejs/node-v0.x-archive/issues/6960 [1] https://github.com/npm/npm/issues/3697

its a long standing issue, and gets worse when there is node_modules inside node_modules inside node_modules ... so on that someone suggested renaming node_modules to n_m . https://github.com/nodejs/node-v0.x-archive/issues/6960#issu...

Ummmm. https://github.com/nodejs/node-v0.x-archive/wiki/Projects,-A... You're right. PayPal, Uber, Walmart are all tiny little nobodies. And I'm not entirely certain what api implementation docs you're looking at, but I've yet to say, "I need service X" and not find a node.js API wrapper already built.

https://github.com/nodejs/node-v0.x-archive/wiki/Projects,-A... Projects like Yammer are really small and not known? Okayyyy. You should really reflect your view of the world.

I have recently started playing around with Ember and trying to get more serious with Vim by using it for this project. I found this page from Joyent to be an awesome resource for setting up Vim with Node: https://github.com/joyent/node/wiki/Vim-Plugins

Original author here -- thanks to everyone for the feedback. Some time has passed since this was originally written and the remaining languages were never updated to improve the safety of the signature verifications. The original reasoning behind this post was to provide a single reference for signature generation and verification in some common languages -- something I struggled to locate myself. Admittedly, I should've provided warnings about using simple and hardcoded keys in the examples, which were done that way for readability. While there is still a lot of debate about the ability to perform true constant-time comparisons in many of these languages (https://bugs.python.org/issue15061, https://github.com/joyent/node/issues/8560) I agree that for those who would be otherwise using the unsafe string comparisons, the benefits certainly

If you're asking if software licenses are important, the answer is yes, they're very important. To the GP, though, I don't immediately see how linking to Chakra in this way would be a license issue. The more important thing is the license information for Node, though, not Chromium: https://github.com/joyent/node/blob/master/LICENSE (some overlap but quite a bit that doesn't)