{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie5tojzcmu342oopwxxwkzqzgerpbx2pf3lpo6cxjdabiehlg3qu4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkoigyppwqn2"
  },
  "path": "/t/pre-rfc-dns-domains-as-package-namespaces/24202?page=3#post_43",
  "publishedAt": "2026-04-30T01:17:29.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "screenshot",
    "done it before",
    "crates.io"
  ],
  "textContent": "> Certain packages may have nicer names, but that doesn't mean that they're the best package implementing that thing for your given use case.\n\nIt ... kinda does, though? The `json` crate might not necessarily work for everything I want to do with JSON (e.g. it doesn't provide an event-based parser), but if you go to `https://crates.io/search?q=json` it's the top spot (screenshot) and seems to be the standard way of dealing with JSON in Rust.\n\nIf I ever do need an equivalent to Go's `json.Decoder` then I'll probably write my own (done it before 18 years ago), and the name of that crate would be `json`.\n\n> `json` gets to use the name `json` simply because it was the first crate that implemented JSON, that doesn't mean it's the best or \"standard\" JSON crate, just that it's the one that got there first.\n\nI understand that the current lack of namespaces means that there can be only one `json` crate on crates.io. This thread is an attempt to convince the team to relax that constraint.",
  "title": "[Pre-RFC] DNS domains as package namespaces"
}