HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
hsiaosiyuan0
naive
Rust2019–2019
hsiaosiyuan0 / naive

naive

Learn JavaScript the hard way 🤯

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

What to know before exploring

What it is

Learn JavaScript the hard way 🤯

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, 5:04:57 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: 2019-07-24 02:43:54 UTC to 2019-07-26 14:30:02 UTC.

012019-07-24 00:00:00 UTC to 2019-07-24 03:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJul 24, 00:002019-07-24 03:00:00 UTC to 2019-07-24 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-24 06:00:00 UTC to 2019-07-24 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-24 09:00:00 UTC to 2019-07-24 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-24 12:00:00 UTC to 2019-07-24 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-24 15:00:00 UTC to 2019-07-24 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-24 18:00:00 UTC to 2019-07-24 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-24 21:00:00 UTC to 2019-07-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-25 00:00:00 UTC to 2019-07-25 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-25 03:00:00 UTC to 2019-07-25 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-25 06:00:00 UTC to 2019-07-25 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 25, 06:002019-07-25 09:00:00 UTC to 2019-07-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-25 12:00:00 UTC to 2019-07-25 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-25 15:00:00 UTC to 2019-07-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-25 18:00:00 UTC to 2019-07-25 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-25 21:00:00 UTC to 2019-07-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-26 00:00:00 UTC to 2019-07-26 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-26 03:00:00 UTC to 2019-07-26 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-26 06:00:00 UTC to 2019-07-26 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-26 09:00:00 UTC to 2019-07-26 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-26 12:00:00 UTC to 2019-07-26 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 26, 12: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
Jul 24, 00:002019-07-24 00:00:00 UTC2019-07-24 03:00:00 UTC110
Jul 24, 03:002019-07-24 03:00:00 UTC2019-07-24 06:00:00 UTC000
Jul 24, 06:002019-07-24 06:00:00 UTC2019-07-24 09:00:00 UTC000
Jul 24, 09:002019-07-24 09:00:00 UTC2019-07-24 12:00:00 UTC000
Jul 24, 12:002019-07-24 12:00:00 UTC2019-07-24 15:00:00 UTC000
Jul 24, 15:002019-07-24 15:00:00 UTC2019-07-24 18:00:00 UTC000
Jul 24, 18:002019-07-24 18:00:00 UTC2019-07-24 21:00:00 UTC000
Jul 24, 21:002019-07-24 21:00:00 UTC2019-07-25 00:00:00 UTC000
Jul 25, 00:002019-07-25 00:00:00 UTC2019-07-25 03:00:00 UTC000
Jul 25, 03:002019-07-25 03:00:00 UTC2019-07-25 06:00:00 UTC000
Jul 25, 06:002019-07-25 06:00:00 UTC2019-07-25 09:00:00 UTC000
Jul 25, 09:002019-07-25 09:00:00 UTC2019-07-25 12:00:00 UTC000
Jul 25, 12:002019-07-25 12:00:00 UTC2019-07-25 15:00:00 UTC000
Jul 25, 15:002019-07-25 15:00:00 UTC2019-07-25 18:00:00 UTC000
Jul 25, 18:002019-07-25 18:00:00 UTC2019-07-25 21:00:00 UTC000
Jul 25, 21:002019-07-25 21:00:00 UTC2019-07-26 00:00:00 UTC000
Jul 26, 00:002019-07-26 00:00:00 UTC2019-07-26 03:00:00 UTC000
Jul 26, 03:002019-07-26 03:00:00 UTC2019-07-26 06:00:00 UTC000
Jul 26, 06:002019-07-26 06:00:00 UTC2019-07-26 09:00:00 UTC000
Jul 26, 09:002019-07-26 09:00:00 UTC2019-07-26 12:00:00 UTC000
Jul 26, 12:002019-07-26 12:00:00 UTC2019-07-26 15:00:00 UTC101

What Hacker News says

2 sources
I have a bit of an off-topic question for anybody who writes Rust. I'm more familiar with web development and higher level languages, but I've always been interested in Rust. While I know a bit of C/C++, I'm far from an expert. One of the things that turns me off from those languages are the frequent use of really short or cryptic variable/function names. I'm looking at this codebase, specifically https://github.com/hsiaosiyuan0/naive/blob/master/src/lib/to..., and I see stuff like `let (s, kv, vk, be) = gen_map!`. I have no clue what those variables would be unless I dug around the rest of the file. Is this sort of variable/method naming convention common in the Rust world? I am not criticizing the author or the language here, merely just curious what I should expect if I dipped my toes into Rust.
In Learn JavaScript the Hard Way

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.