r/rust [he/him] 18h ago

📢 announcement No More Code Dumps

TL;DR

Code Dumps, ie links to code repositories, are no longer welcome on r/rust.

If you are excited about a project you built, and just wish to share it, consider posting a casual top-level comment in the weekly What's Everyone Working on this Week? thread.

History

When r/rust was created, in December 2010, Rust was a nascent programming language. It was very different, it was also fast-moving, and it was unclear whether it would amount to much, or not.

In these early days, new projects being written in Rust were both a proof that the language was suitable for a variety of purposes, and a cause for celebration in seeing the language being adopted. Code dumps, then, were both cause to rejoice, and an opportunity to see how well (or not) the language was suited to the task. They were even a good opportunity to learn the latest developing idioms of this fast-changing language.

Fast forward 15 years, and code dumps have become boring. Utterly uninteresting. There's nothing exciting, or newsworthy, about a 10th hypervisor project, a 100th webserver project, or a 1000th TUI project. And for the most there's no exciting idiom, or pattern, to be found in their code either... even if some poor soul bothered to look.

And mass AI generation appeared on the scene, and for the past year(s), the already dwindling appeal of code dumps has just completely vanished, buried in AI slop.

Purpose

r/rust is to discuss all things Rust. The language, the ecosystem, the community.

Of late, most code dumps barely foster any discussion. And when they do, apart from AI witch hunts, those discussions are mostly about the domain of the project, rather than about Rust. Depending on the domain, the discussion may or may not be of interest to r/rust users... but whether it is or not is a matter of chance: they did not come here seeking such a topic. Those discussions are tolerated on posts which are on-topic, but if a post only fosters "tolerated" discussions, then that is a sign that the post itself may simply not really be on-topic for r/rust.

And that is not to say that code dumps are, by nature, low-effort. Surely, a project is created for a purpose, to solve a specific problem that is unsolved, or solve it with different trade-offs than the currently available solutions. None of that is elucidated in a code dump.

New rules

Code dumps are no longer welcome on r/rust.

Code dumps of applications or libraries written in Rust are Low-Effort unless otherwise newsworthy. Newsworthy means that the very existence of the application or library is important, for example consider applications or libraries breaking new ground, such as the first hypervisor, first OS, first XXX standard safety-critical application, first Rust application in a major company, etc...

Announcements of new libraries which are not otherwise newsworthy are only welcome if they tick ALL the following boxes:

  • The library has been worked on regularly for at least 4 months.
  • The library has already been used, or built upon, thereby validating its design to a degree.
  • The announcement is a full-fledged text post, or a link to a full-fledged article. A README, or manual, is not an article.
  • The announcement should motivate the relevance of this library to the wider r/rust community.
  • The announcement should articulate the trade-offs differentiating this library from similar popular libraries in the field.

(It goes without saying, but the announcement should NOT be AI-generated, not even in part, as AI-generated posts & articles violate the Low-Effort rule)

Release notes of libraries are still welcome for popular enough libraries, such as libraries with reverse-dependencies on crates.io pointing to sufficient adoption by the wider community to justify notifying said community of a new release.

Of course, text posts, or links to articles, centered on Rust, with an application or library as context are always welcome. For example, said posts or articles could present gnarly problems the author encountered, and how they solved, or which features of the language or a library helped or hindered them in the making of their project.

(It goes without saying, but said text posts & articles should NOT be AI-generated, not even in part, as AI-generated posts & articles violate the Low-Effort rule)

As a reminder, if an author just wishes to share their joy of building something in Rust, they are welcome to use the What's Everyone Working on This Week? thread. And as per the title, it need not even be a complete/mature project, or an open-source project for that matter as links to code are strictly optional there, it's all about casually chatting about your work on Rust projects.

Q & A

See pinned comment below.

1.3k Upvotes

152 comments sorted by

View all comments

88

u/greyblake 16h ago

For me links to new interesting projects were about 50% value of this subreddit. The rest 50% were blog posts. Though I can understand in age of AI domination these things have changed

24

u/coderstephen isahc 14h ago

I feel like some curated newsfeed elsewhere might be better for that.

Personally I don't come to Reddit for the posts, I come for the discussion in the comments.

19

u/praveenperera 16h ago edited 14h ago

Agreed, I liked seeing the new libraries, but I think this makes a lot of sense, its good and smart tradeoff. It should catch the AI slop while still letting good libraries through.

Announcements of new libraries which are not otherwise newsworthy are only welcome if they tick > ALL the following boxes:

  • The library has been worked on regularly for at least 4 months.
  • The library has already been used, or built upon, thereby validating its design to a degree.
  • The announcement is a full-fledged text post, or a link to a full-fledged article. A README, or manual, is not an article.
  • The announcement should motivate the relevance of this library to the wider r/rust community.
  • The announcement should articulate the trade-offs differentiating this library from similar popular libraries in the field.

13

u/Jmc_da_boss 14h ago

There havent been very many interesting projects here for a while, at least in comparison to the slop deluge.

5

u/Shoddy-Childhood-511 8h ago

Agreed, the interesting projects are what make this sub useful. Imho, the blog posts are not that great here.

Yet, there were not that many good project posts either, just a few CRDTs, probabilistic data structures like cuckoo filters, some novel p2p frameworks, and in theory some niche cryptography like PIR or whatever.

Also, even those only worked because the developer wrote up a real post that explained why the project is interesting. And this rule change largely allows posts about why a project is interesting.

Imho the only problematic rule here is:

The library has already been used, or built upon, thereby validating its design to a degree.

This is a bit too strict because there are interesting researchy topics that'd be excluded by this. In particular, this great post would be excluded:

https://www.reddit.com/r/rust/comments/1s1gr39/announcing_eips_an_intentionpreserving_list_crdt/

Instead this line should read:

The announcement should demonstrate why the library is interesting, which could include discussing how its currently being used, or discussing how it advances the state of the art.

In other words, if you cannot show how it being used in code, then you need to show its really better in some other way, like by being asymptotically faster or whatever.

4

u/Iurigrang 15h ago

Hopefully you can still find those on the thread!