MAmasihyeganeh·Dec 24, 2014Submission
Empty Node Module Memory Usage
2 points · Open discussionnodejs
node-v0.x-archive
Web Development2010–2021
nodejs / node-v0.x-archive · Archived
node-v0.x-archive
Moved to https://github.com/nodejs/node
165Distinct people
182Mentions
1Explicit recommenders
34.3KGitHub stars
What to know before exploring
What it is
Moved to https://github.com/nodejs/node
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
Although I have never built a "complete website" on the node.js stack, the time that I have spent developing on the platform has been very enjoyable and I've put a decent…
kersny used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- nodejs/node · linked in 4 of the same discussions
- caolan/async · linked in 2 of the same discussions
- cskr/grasshopper · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year182 dated mentions
Observed mentions: 2010-06-11 19:12:27 UTC to 2021-04-14 02:35:01 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2010 | 2010-01-01 00:00:00 UTC | 2011-01-01 00:00:00 UTC | 16 | 4 | 12 |
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 48 | 6 | 42 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 28 | 4 | 24 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 27 | 4 | 23 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 31 | 7 | 24 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 20 | 3 | 17 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
31 sourcesNode v0.10.34 causes untrusted cert errors
2 points · Open discussionBy adapting the highWaterMark option one could probably tweak it even further.
Default buffer size seems to be 64k: https://github.com/joyent/node/blob/912b5e05811fd24f09f9d652...
Stream buffering: http://www.nodejs.org/api/stream.html#stream_buffering
In Node.js stream handbookThose are decent points, but I'd think Io.js would have more reasons.
First of all, if you implement a polyfill in JavaScript, it'll be translated into pretty fast native code. But even if it didn't, most(?) of Node's core libraries are written in plain JavaScript and presumably are as fast as any module in npm. Take a look: https://github.com/joyent/node/blob/master/lib/buffer.js
And if you really want optimized native code, npm supports that out of the box. I kinda dislike npm modules that require a compilation step, but they're out there.
As for robustness, there's nothing stopping one to making robust node modules that are not in the core.
In Node.js is forked, not fuckedThis is a big deal, because of who is involved. Here's the list of people involved:
* Indutny (listed as a Node.js code team member)
* Trevor Norris (also a Node.js core team member)
* Isaac Schlueter (cited as a Node.js core team alumni)
* Ben Noordhuis (also an alumni)
* Bert Belder (another alumni and a Node.js maintainer)
Compared to the Node list of top contributors:
https://github.com/joyent/node/graphs/contributors
Here's some better information:
http://www.infoworld.com/article/2855057/application-develop...
In IO.js, a Node forkCompare with https://github.com/joyent/node, similar readme and commit numbers. Looks like a node.js fork. (EDIT: maybe you already understood that, I thought it might have been a different thing from node.js altogether until I saw the repositories shared a README/history)
In IO.js – Evented I/O for V8 javascriptDid it seem bad a year ago? 2? 3? It's always been that way. 3 years ago, when ry was still on the project, it was only 30 days delta [0][1]. Joyent has chosen to increase the Technical Debt in order to increase overall Node Stability. Pick your poison.
[0] https://github.com/v8/v8/tree/3.6.6
[1] https://github.com/joyent/node/commit/0ba8f05a423df0e2ef53fc...
In Node.js production ships unmaintained version of v8Yes times 1,000!
This is what we're trying to address at Sourcegraph (https://sourcegraph.com/). 80% of programming is about reading and understanding code, not writing code.
Why don't existing tools focus more on helping people read and understand code--and, more broadly, collaborate on a development team? Things like:
* seeing everywhere a function or class is used, in context (like https://sourcegraph.com/github.com/joyent/node/.CommonJSPack... on the right side)
* seeing who at your company knows the most about an area of your codebase
* seeing the history of changes, in terms of functions/modules added, not just lines (like https://sourcegraph.com/github.com/fsouza/go-dockerclient/.c...)
* having a long-lived discussion about a module/class/function that doesn't vanish after a commit is merged or the file's lines shift around
So far,
Read the rest
most of the innovation in programming tools has been in editors or frameworks, not in collaboration and search tools for programmers.
While there are great editors and frameworks, the lopsidedness is unfortunate because making it easier for programmers to learn and reuse existing code and techniques, and to collaborate on projects, can have a much bigger impact than those other kinds of tools. That's because, in my experience, the limiting factors on a solo developer's productivity are the editors and frameworks she uses, but the limiting factor on a development team's productivity is communication (misunderstanding how to use things, reinventing the wheel, creating conflicting systems, not syncing release timelines, etc.).
I've not seen any ill will towards you from the people I named above, at least not publicly. They all know it was your project and you were free to do with it as you saw fit. They disagree with your choice, but it was yours to make. You had good intentions, even if the actions played out badly, but that's all now in the past.
Strongloop, on the other hand, has the ability to change the outcome, and have chosen not to. They've been given loads of evidence of what the maintainers want them to do, and so far their actions have not demonstrated a desire to resolve the conflict. Their public responses have been entirely self-serving and barely apologetic.
I am firmly of the impression that they want to hold on to Express so they can claim it's development as an R&D tax write-off. This fits with why they've stated they would only give it to an
Read the rest
organization backed by a non-profit foundation, since then it could continue to be a charitable donation. They want to make money off this situation, and that's basically thumbing their noses at the people who put their time into it for free.
As I said in the github thread, there are some major differences between this situation and when Ryan sold to Joyent. Ryan was still working on Node, and Joyent hired both him and Isaac to continue doing so. They also announced [1][2] the transition before it happened, made it very clear what was happening in terms of code ownership, and answered everyone's questions ahead of time. The repos didn't transfer until four months later [3].
[1] https://groups.google.com/forum/#!topic/nodejs/lWo0MbHZ6Tc
[2] https://www.joyent.com/blog/a-new-abode-for-node
[3] https://github.com/joyent/node/commit/45adc907c9b3eff0bc560d...
edit: I'm being told Strongloop is actually helping to create a foundation for Express to be owned by, they're just not doing it publicly. So that's good.
Such as?
I'm pretty sure Chromium and Node build just fine.
https://github.com/joyent/node/wiki/installation
http://www.chromium.org/developers/how-tos/build-instruction...
EDIT:
https://github.com/breach/exo_browser/wiki/Building-the-ExoB...
What else am I missing from your package.json?
In Show HN: Breach – A modular browser built on Chromium and Node.jsLove the idea! I tried it by searching for Node's require. It did point me to the right source [1], but the usage examples are all minified and unreadable. Might want to check for a maximum size on the usage examples that are presented.
[1] https://sourcegraph.com/github.com/joyent/node/.CommonJSPack...
In Sourcegraph: Search code, jump around source, see real usage examplesAs far as I understand it the problem _is_ with Node -- specifically module.js [0] which is what defines require() and its recursive lookup behavior.
[0] https://github.com/joyent/node/blob/master/lib/module.js
In Node's nested node_modules approach is basically incompatible with WindowsNode's nested node_modules approach is basically incompatible with Windows
63 points · Open discussionI disagree. I think fault lies with the language designer(s) for putting the equivalent of a pull-handle on a push-door. The only way to reliably avoid this error would be to spend an inordinate amount of time reading documentation, dutifully examining every aspect of basic functionality for unusual behavior. Every other string replace method I've encountered does global replace. Java's String.replace(), STL's std::replace, PHP's str_replace, Python's string.replace(), all of them replace every instance. Given this precedence, it's entirely reasonable to assume JavaScript works the same. Unfortunately, it doesn't.
I've been writing JavaScript off-and-on since I was 12. I've used Node.js extensively enough to find bugs in it, including one that ended up being a bug in V8[1][2]. If I'm not an experienced JavaScript developer, then very few
Read the rest
Showing the 15 most recent of 31 sources. Enable JavaScript to search and browse every indexed mention.