cross-posted from: https://programming.dev/post/1825728

Lots of new features!

Thought I should share this with those who don’t use users.rust-lang.org. Note: I’m not affiliated with lib.rs, I’m only reposting to lemmy.

4 points

Its too bad they closed sourced the site. I really like the way it makes exploring crates easy, but after major devs having their crates removed Im very hesistant to use it.

permalink
report
reply
2 points
*

Neat! And for anyone not familiar Lib.rs is a package repository, described as an alternative [frontend] to Crates.io.

permalink
report
reply
2 points

Not really: lib.rs is a different website frontend to the same old crates.io, presenting the data in a better way.

permalink
report
parent
reply
1 point

lib.rs has a pretty UI, but the dev kinda sucks, and after the latest controversies, using it leaves a bad taste in my mouth. Crates.io is good enough.

permalink
report
reply
1 point

The drama sucks, agreed. But crates.io is lightyears behind in design, search and features.

For example: Lib.rs has the first thing I want to know (when was the last release, is this still developed?) right at the top. For crates.io that is hidden near the bottom, especially on mobile.

Also: Lib.rs has search that actually works and finds relevant things, I cannot say that for crates.io.

I would love for crates.io to take (some) inspiration from lib.rs.

Finally: I share the lib.rs author’s opinion on cryptocurrency, though I don’t agree with his extreme measures. (If it was me I would put a note in neutral tone that crypto is problematic for the environment on the relevant categories and crates, with some links to more into, then leave it at that.) So using lib.rs despite the drama doesn’t bother me that much.

permalink
report
parent
reply
1 point

Hey, maybe this will actually lead to standardization of feature documentation? It’s been in terrible shape for years. The fact that optional dependencies and features have been treated nearly the same by cargo, but treated differently by crates.io, makes it useless for discovering features for crates. Up until now, my go-to method is to examine the Cargo.toml file directly, and if I can’t figure out what a feature does there I look directly at the source code.

permalink
report
reply

Rust Lang

!rustlang@lemmyrs.org

Create post

Rules [Developing]

Observe our code of conduct

  • Strive to treat others with respect, patience, kindness, and empathy.
  • We observe the Rust Project Code of Conduct.
  • Submissions must be on-topic
  • Posts must reference Rust or relate to things using Rust. For content that does not, use a text post to explain its relevance.
  • Post titles should include useful context.
  • For Rust questions, use the stickied Q&A thread. [TBD]
  • Arts-and-crafts posts are permitted on weekends.
  • No meta posts; message the mods instead.

Constructive criticism only

  • Criticism is encouraged, though it must be constructive, useful and actionable.
  • If criticizing a project on GitHub, you may not link directly to the project’s issue tracker. Please create a read-only mirror and link that instead.
  • Keep things in perspective
  • A programming language is rarely worth getting worked up over.
  • No zealotry or fanaticism.
  • Be charitable in intent. Err on the side of giving others the benefit of the doubt.

No endless relitigation

  • Avoid re-treading topics that have been long-settled or utterly exhausted.
  • Avoid bikeshedding.
  • This is not an official Rust forum, and cannot fulfill feature requests. Use the official venues for that.

No low-effort content

  • Showing off your new projects is fine

No memes or image macros

  • Please find other communities to post memes

No NSFW Content

  • There are many other NSFW communities, let’s keep this related to the language

Community stats

  • 1

    Monthly active users

  • 79

    Posts

  • 135

    Comments