HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nodejs
node-v0.x-archive
Web Development2010–2021
nodejs / node-v0.x-archive · Archived

node-v0.x-archive

Moved to https://github.com/nodejs/node

Web Development
Explore on GitHubRead Hacker News discussions
165Distinct people
182Mentions
1Explicit recommenders
34.3KGitHub stars
REPOSITORY AT A GLANCE

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

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, 6:01:08 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.

010203040502010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 16 mentions; 4 submissions, 12 comments20102011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 48 mentions; 6 submissions, 42 comments2012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 28 mentions; 4 submissions, 24 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 27 mentions; 4 submissions, 23 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 31 mentions; 7 submissions, 24 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 20 mentions; 3 submissions, 17 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC16412
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC48642
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC28424
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC27423
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC31724
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC20317
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC505
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC110
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC303
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

28 sources
beatgammit·Oct 31, 2012
I agree with this statement, but I would add a fourth: 4) What are the potential rewards? Assuming a magical node.js script existed, the backend resources needed are immense, with no up-front profit. The http server mentioned needs to be hosted somewhere, and that somewhere has to be known by the user so he can tell his friends to go to some.domain.com:1773/instance. Also, the overhead of the latency would negate the usefulness of running any code on the client. In those 30 ms that it takes to tell the client a request has come in, the server could already have responded. This hammers the NIC for little gain. Sure, it's a cool idea, but it's not going to net any real profit (unless you can convince some VCs to ignore logic and give $$ based on "cool"). I'd rather see a simple node instance hoster, where you can upload code and have it run
Read the rest
publicly: https://github.com/joyent/node/wiki/Node-Hosting If I wanted the code to run on the client, I'd also like to see a kind of folding@home that distributes data sets to clients. That idea has real potential for profit, and doesn't require nearly the resource investment of node.js running in a browser. However, for a "cool" side-project with no intent for profit, I agree, improving 1) will drastically increase hobbyist interest. Hobbyists have their own ideas as well.
In NodeJS Runtime for Chrome
grncdr·Oct 14, 2012
I don't think it is. I seem to recall Isaac saying that he considers require.extensions to be a mistake, though I don't know if he meant the concept (extensibility) or implementation (register hooks under filename extensions). Either way, I think it's recognized that a lot of people enjoy and use the functionality so it's unlikely to go away. As an aside, here's the relevant bit of code that loads the (already compiled) source as a module: https://github.com/joyent/node/blob/master/lib/module.js#L40...
In Sweet.js - Sweeten your Javascript (by Mozilla)
olalonde·Oct 1, 2012
Hey, I'm currently evaluating a number of Node.js web frameworks for a project I'm working on (I'll eventually publish the results on my blog). So far, I have reviewed: RailwayJS, Locomotive[0], Tower.js[1], GeddyJS[2], Derby[3] and Meteor[4]. It would be really great if you could give me your opinion on how RailwayJS compares to those (especially Tower.js, GeddyJS and Locomotive as they seem to be competing directly). [0] http://locomotivejs.org/ [1] http://towerjs.org/ [2] http://geddyjs.org/ [3] http://derbyjs.com/ [4] http://meteor.com/ ... more Node.js web frameworks: https://github.com/joyent/node/wiki/modules#wiki-web-framewo...
In RailwayJS
pooriaazimi·Jun 6, 2012
Oh, and I don't know where Joyent announced this news - it certainly wasn't on their blog... and the article doesn't provide any source. The only time I saw anyone mention anything about 0.8's release date, was here: https://groups.google.com/d/msg/nodejs/aRC2pbFN8NU/YXpB_vuCT... There are (at least) 7 more open issues before 0.8: https://github.com/joyent/node/issues?milestone=10&state... -- I feel guilty upvoting this story; specially given that submitter is just a dummy account promoting this blog.
In Node.js v0.8 around the corner
aGHz·Apr 26, 2012
Manually, you could structure it in several functions like prepare_response() and render_response(), possibly with other functions in-between for the various chunks of data you need in your response. When all the chunks are ready, you finally call render_response() and send it. In practice, you can find a ton of libraries that can help you manage this [1], I -believe- the most recommended one would be 'futures'. [1] https://github.com/joyent/node/wiki/modules#wiki-async-flow
In Beginning Node.js Development

Showing the 15 most recent of 28 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.