{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigywwum6gpefc6cbtmopjbcpuqjmmxjgffujff6guuqhtsk7zk7lu",
    "uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3mh6g5bsobvk2"
  },
  "path": "/post/47261682",
  "publishedAt": "2026-03-15T20:46:19.000Z",
  "site": "https://programming.dev",
  "tags": [
    "Rust",
    "cows_are_underrated",
    "22 comments"
  ],
  "textContent": "submitted by cows_are_underrated to rust\n63 points | 22 comments\n\nI recently started learning rust, and I was ready for one hell of a fight. I heard all those horror Storys about the compiler complaining about every single detail and that developing rust means having a constant fight with the compiler about seemingly irrelevant things. However, so far I have to tell, that while its somewhat true, that the compiler is somewhat picky, it is incredibly helpful. Never before have I seen such good and helpful compiler messages. It not only says what you did wrong, but also gives direct help on what to do to fix your code. I also really like, that it gives you direct references to the rust book in the compiler messages.\n\nPrior to starting my journey with rust I did quite a lot of python, some C and some bash and their interpreter/compiler messages are nothing when comparing them with rust. Especially the bash error messages are awful if you do not know what they mean and how to fix them.",
  "title": "The Rust Compiler is the most helpful one I have experienced so far"
}