HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
alex
libuv
C2013–2013
alex / libuv

libuv

Cross-platform asychronous I/O

2Distinct people
2Mentions
0Explicit recommenders
1GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Cross-platform asychronous I/O

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 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 3-hour interval2 dated mentions

Observed mentions: 2013-12-01 00:07:51 UTC to 2013-12-04 06:46:29 UTC.

012013-12-01 00:00:00 UTC to 2013-12-01 03:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 1, 00:002013-12-01 03:00:00 UTC to 2013-12-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-01 06:00:00 UTC to 2013-12-01 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-01 09:00:00 UTC to 2013-12-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-01 12:00:00 UTC to 2013-12-01 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-01 15:00:00 UTC to 2013-12-01 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-01 18:00:00 UTC to 2013-12-01 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-01 21:00:00 UTC to 2013-12-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-02 00:00:00 UTC to 2013-12-02 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-02 03:00:00 UTC to 2013-12-02 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-02 06:00:00 UTC to 2013-12-02 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-02 09:00:00 UTC to 2013-12-02 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-02 12:00:00 UTC to 2013-12-02 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-02 15:00:00 UTC to 2013-12-02 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 2, 15:002013-12-02 18:00:00 UTC to 2013-12-02 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-02 21:00:00 UTC to 2013-12-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-03 00:00:00 UTC to 2013-12-03 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-03 03:00:00 UTC to 2013-12-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-03 06:00:00 UTC to 2013-12-03 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-03 09:00:00 UTC to 2013-12-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-03 12:00:00 UTC to 2013-12-03 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-03 15:00:00 UTC to 2013-12-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-03 18:00:00 UTC to 2013-12-03 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-03 21:00:00 UTC to 2013-12-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-04 00:00:00 UTC to 2013-12-04 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-04 03:00:00 UTC to 2013-12-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-04 06:00:00 UTC to 2013-12-04 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 4, 06:00

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
Dec 1, 00:002013-12-01 00:00:00 UTC2013-12-01 03:00:00 UTC101
Dec 1, 03:002013-12-01 03:00:00 UTC2013-12-01 06:00:00 UTC000
Dec 1, 06:002013-12-01 06:00:00 UTC2013-12-01 09:00:00 UTC000
Dec 1, 09:002013-12-01 09:00:00 UTC2013-12-01 12:00:00 UTC000
Dec 1, 12:002013-12-01 12:00:00 UTC2013-12-01 15:00:00 UTC000
Dec 1, 15:002013-12-01 15:00:00 UTC2013-12-01 18:00:00 UTC000
Dec 1, 18:002013-12-01 18:00:00 UTC2013-12-01 21:00:00 UTC000
Dec 1, 21:002013-12-01 21:00:00 UTC2013-12-02 00:00:00 UTC000
Dec 2, 00:002013-12-02 00:00:00 UTC2013-12-02 03:00:00 UTC000
Dec 2, 03:002013-12-02 03:00:00 UTC2013-12-02 06:00:00 UTC000
Dec 2, 06:002013-12-02 06:00:00 UTC2013-12-02 09:00:00 UTC000
Dec 2, 09:002013-12-02 09:00:00 UTC2013-12-02 12:00:00 UTC000
Dec 2, 12:002013-12-02 12:00:00 UTC2013-12-02 15:00:00 UTC000
Dec 2, 15:002013-12-02 15:00:00 UTC2013-12-02 18:00:00 UTC000
Dec 2, 18:002013-12-02 18:00:00 UTC2013-12-02 21:00:00 UTC000
Dec 2, 21:002013-12-02 21:00:00 UTC2013-12-03 00:00:00 UTC000
Dec 3, 00:002013-12-03 00:00:00 UTC2013-12-03 03:00:00 UTC000
Dec 3, 03:002013-12-03 03:00:00 UTC2013-12-03 06:00:00 UTC000
Dec 3, 06:002013-12-03 06:00:00 UTC2013-12-03 09:00:00 UTC000
Dec 3, 09:002013-12-03 09:00:00 UTC2013-12-03 12:00:00 UTC000
Dec 3, 12:002013-12-03 12:00:00 UTC2013-12-03 15:00:00 UTC000
Dec 3, 15:002013-12-03 15:00:00 UTC2013-12-03 18:00:00 UTC000
Dec 3, 18:002013-12-03 18:00:00 UTC2013-12-03 21:00:00 UTC000
Dec 3, 21:002013-12-03 21:00:00 UTC2013-12-04 00:00:00 UTC000
Dec 4, 00:002013-12-04 00:00:00 UTC2013-12-04 03:00:00 UTC000
Dec 4, 03:002013-12-04 03:00:00 UTC2013-12-04 06:00:00 UTC000
Dec 4, 06:002013-12-04 06:00:00 UTC2013-12-04 09:00:00 UTC101

What Hacker News says

2 sources
> I don't know how much truth there is to that, but as a general spectator I feel like wanting to remark that Bryan Cantrill only fanned the fire here in all of this. Pretty much every participating party in this whole thing came out looking like a loser, Joycent, Strongloop, the whole nodejs scene. Here's hoping Ben now finds a workplace that appreciates him for his talents and respects him as a person. If he's butthurt over such a tiny change (one that is entirely legitimate, all things considered) in documentation, they're right for calling him an asshole. Seriously, go look at the diff that he had such an issue with: https://github.com/alex/libuv/commit/1ff9d18d398fb9f35b72fa0... He could have just smooshed the big green button and scored one for the "not pointlessly defaulting to masculine terms" team, but instead he had to turn it i
Read the rest
nto an "omfg no this is stupid" debate. Inequality doesn't change by embracing the status quo simply because that's how we've always done things. As much as Joyent look like turds here, they did the right thing. If he'd worked for me, I'd have fired him for such assholery too. We're talking about a one-line documentation change of "him" to "they", for fuck's sake.
In Ben Noordhuis's Departure

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.