1. 55

    1. 5

      Really excited about the Cargo registry changes here. Another step forward to less reliance on crates.io

      1. 14

        Especially because crates.io is powered by GitHub under the hood and you need a GitHub account to publish crates, so the Microsoft enshittification being forced on all the devs is inevitable. Biggest risk when building something with Rust in my opinion. If you have 100 dependencies - and this happens very quickly when you build GUI or web applications - then you will have a hard time not relying on crates.io.

        1. 20

          Eh, I don’t want to get super off-track, but I would hazard that Microsoft has been a good steward for GitHub. But I agree crates.io shouldn’t require a GH account to publish.

        2. 12

          In case anyone’s wondering, there’s no objection by the team to supporting different authentication methods - there are some practical matters, and seemingly a bit of tech debt from the historical use of GH, and if someone is willing to do the work then alternate providers would be accepted.

        3. 1

          At the very least if you run your own registry you could mirror the crates.io dependencies, though then you need to either have a syncing system or manually mirror new versions as you upgrade your dependencies.

          1. 1

            Here’s a script to mirror all of crates.io: https://github.com/progval/crates.io-mirror in a way that should be usable both from a web browser and from Cargo.

            I haven’t ran it in a while, I expect it to take about 200GB now.

            1. 1

              That’s a bit expensive in comparison, but I guess it could probably be modified to do it based in your dependencies. :)

    2. 2

      Oh no, did async trait not make it for 1.74? Does anybody know the reason?


      1. 5
      2. 2

        It was never slated for 1.74 because the beta branch that ended up as 1.74 was cut before the PR landed.