HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
joyent
libuv
C2011–2025
joyent / libuv · Archived

libuv

Go to

77Distinct people
86Mentions
1Explicit recommenders
3.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Go to

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

luriel wrote a nice answer, like a good, old hater would write. (You can't just go around and insult programming languages. They have feelings too, dude.) is there any real…

b3tta 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

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:27:21 AM 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 year86 dated mentions

Observed mentions: 2011-07-20 15:45:57 UTC to 2025-12-07 08:01:36 UTC.

0102030402011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 44 mentions; 4 submissions, 40 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 22 mentions; 1 submissions, 21 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

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
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC202
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC716
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC44440
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC22121
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC303
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC303
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
libuv has moved to github.com/libuv/libuv
Read the full README on GitHub

What Hacker News says

3 sources
That's not the reason, and you know it. "On the one hand, it seems ridiculous (absurd, perhaps) to fire someone over a pronoun -- but to characterize it that way would be a gross oversimplification: it's not the use of the gendered pronoun that's at issue (that's just sloppy), but rather the insistence that pronouns should in fact be gendered." https://www.joyent.com/blog/the-power-of-a-pronoun The biggest issue is the way that you handled this. You did this appallingly. You still seem to be puzzled why people still bring this up. In a community project, people often do things you aren't going to like. Ben rejected a push, and he steadfastly maintains that he did this for good reasons: https://github.com/joyent/libuv/pull/1015#issuecomment-29568... Now instead of communicating with Ben, giving him the benefit of the doubt as a non-native
Read the rest
speaker of English and calling him out publicly in the way you did was an absolute classic case of what you do NOT do. In a community run project, the dynamics are different to being in a corporation. The first rule is: you are dealing with a lot of people, from a lot of different backgrounds. There is lots of room for misunderstanding. The absolute golden rule around dealing with a popular project is to try to wrangle this appropriately and with as little heat as possible. So let's review what you did: 1. You posted one of the most inflammatory, aggressive posts I've seen in a very long time. You took no time to talk to Ben about his position and to talk him around to making an apology and reversing his decision. 2. You compete with StrongLoop. You basically told your competitor that they should fire one of their best developers to the project. Your company may have been a main initiator of Node.js and you see it as largely the steward for the project, but your own employee reversed the decision of a major contributor. And this is where you really stuffed up. For some time there had been rumblings about how Joyent was biased about the way they accepted commits and directed the project - rightly or wrongly. There was a perception of bias towards Joyent's interests. That's not necessarily a correct viewpoint. But you started a chain of events you now can't control. Joyent has finally setup a Foundation, but has now got a fork competing with the core project. StrongLoop is one of the groups backing io.js. A large number of your core developers are publicly backing io.js. 3. Community leaders, like yourself, aren't meant to send abusive messages over blogs. You called him an arsehole. You called for his sacking. Let's underscore how tone-deaf you have been, and completely clueless over how to run an open source project: "While we would fire Ben over this, node.js is an open source project and one doesn't necessarily have the same levers. Indeed, one of the challenges of an open source project that depends on volunteer effort is dealing with assholes" You don't realise how much damage you did. I agree with gender neutral language in technical writing. Many others do as well. If you had dealt with this differently and not decided to become a self-aggrandizing pundit, then you would have probably shown that Joyent can deal with controversial matters maturely and civilly, play nicely with others, resolve conflict, and you'd have the high moral ground. Now you just look like a bully, and I'd say you were the catalyst for the io.js fork. You also opened yourself up to your own past, which you also regret. As I say - you've basically given us all a text-book case study into how not to manage an open source project. P.S. FWIW, I upvoted you.
In How One Stupid Tweet Blew Up Justine Sacco’s Life
I was interested myself, so I did a little google-foo. So Ben Noorddhuis was a major contributor to NodeJS and a volunteer (that is, not a Joyent employee). It turns out Ben rejected a pull request that would have made pronoun in the document gender neutral. The documents were already grammatically correct, but whoever made the pull request had a political preference for using a non masculine pronoun. Ben rightly saw this a trivial change. But the political harpies made an issue of it. Joyent put an embarrassing and immature blog posting which essentially called Ben an "Asshole" and said that if he was an employee he'd be fired. https://www.joyent.com/blog/the-power-of-a-pronoun Ben, on the other hand, handled himself quite well. https://github.com/joyent/libuv/pull/1015#issuecomment-29568... https://news.ycombinator.com/item?id=68452
Read the rest
In Io.js 1.0.0

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.