HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
rust-lang
www.rust-lang.org
Fluent2018–2023
rust-lang / www.rust-lang.org

www.rust-lang.org

The home of the Rust website

7Distinct people
7Mentions
0Explicit recommenders
399GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The home of the Rust website

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, 3:56:07 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 year7 dated mentions

Observed mentions: 2018-11-30 00:05:49 UTC to 2023-11-22 16:06:37 UTC.

01232018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-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 comments2023

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
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC312
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
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

What Hacker News says

7 sources
I've used Rust a bit, but not enough to know the details of how cargo and crates.io approach managing collected information. There seems to be an open issue and WIP PR with more details: Issue: https://github.com/rust-lang/crates.io/issues/955 PR: https://github.com/rust-lang/www.rust-lang.org/pull/919/file... The cargo manifest also supports things like: The publish field (optional) The publish field can be used to prevent a package from being published to a package registry (like crates.io) by mistake, for instance to keep a package private in a company. [package] # ... publish = false But I would be curious if someone more knowledgeable than myself would be interested in giving a quick summary of the approach?
In Go 1.13 Release Notes

Rust website design qualm

https://i.ibb.co/FXrV7QG/ruts.png https://i.ibb.co/mX2tR5P/ruts2.png I was wondering if it is just me or does anyone struggle to read this text? Its a legitimate issue and I know I can't change the rust designer's mind by asking them nicely. I looked through the github issues for the same and apparently they just close the issues relating to design changes without consideration: https://github.com/rust-lang/www.rust-lang.org/issues/468#issuecomment-443150282 @steveklabnik: Please, atleast make it legible. It looks like some designer took it upon their ego to reject any design feedback, as I have noticed in the earlier discussions. Not a good impression for an open source project. I am sorry for coming across as rude but wanted to bring more attention to it here.
6 points · Open discussion
> Please file an issue with any feedback you have! We’re also looking for people with abilities of all kinds to help maintain the site, and especially people with design, CSS, and marketing skills. If you’d like to get involved, please email us! Just a reminder that if you've got some time to type out a comment in this thread voicing your dissatisfaction you could type that comment out into a Github issue[0] and become a certified open source contributor(tm)! One of the best things about rust is it's community and it's willingness to change and find better ways to do things. [0]: https://github.com/rust-lang/beta.rust-lang.org/issues/new/c...
In A new look for rust-lang.org
We hired a designer. We're not frontend devs, but do have people who have some experience with this. Please file bugs! https://github.com/rust-lang/beta.rust-lang.org/issues/new/c... Some of this is stuff we know, and are tweaking. As the blog post about this says, this is a beta, and we have a lot more work to do. For example, the calendar thing: it's temporary. It's not trivial to style. There's been zero optimization work, which is a lot of what your comment is about. We didn't want to invest in that until we got the big picture stuff down.
In A new look for rust-lang.org

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.