It just looks like stdx has copied stuff from crates and put it in a git repo. It feels like this is worse than a package manager? As in why would I trust a random git repo to keep things up to date over the officially published channel?
Plus, with forks anyone can publish a commit accessible from the main repo, so one could disguise a malicious version of stdx by forking the repo, pushing their charges, then setting the rev: base64 = { git = "https://github.com/rust-stdx/stdx", rev = " " }
Why stdx is not on crates.io
21–30 of 71 posts
Re: Why stdx is not on crates.io
#22And in general, people pointing at Rust "limited" stdlib (it's only limited compared to Python) as one of the big issue and risk with rust are, in my opinion, misguided. You will never make an stdlib big enough to remove the need for external dependencies. It also creates a bunch of other problems. Actually, to take Python as an example, some functionality being in the stdlib have created a bunch of issue over the years since you can't just introduce breaking changes in an stdlib as easily. Look at urllib2/3 or xml in python. In the end, almost everyone ends up using requests and lxml instead. There are many issues that need to be dealt with to mitigate supply chain attacks. A bigger stdlib or an "stdlib-extended" a la Boost, is not one of them.
Also, specifically for Rust, many people run in a no-std environment (anything sized constraint for the most part). So another stdlib would do nothing for them.
Re: Why stdx is not on crates.io
#23stdx is not the best example. The most popular package that is not on crates.io is probably embassy. Also Debian tries to build and distribute independently from crates.io. So crates.io is important but is not the (Rust) world.
Re: Why stdx is not on crates.io
#24stdx is not the best example. The most popular package that is not on crates.io is probably embassy. Also Debian tries to build and distribute independently from crates.io. So crates.io is important but is not the (Rust) world.
There's no single "embassy" crate, but all the components (HALs, executor, usb, net, etc.) are all on crates io and have been for a long time.
Re: Why stdx is not on crates.io
#25> Also, you can only create a crates.io account with a GitHub account Oh is that true? They tied themselves to Microsoft it seems. What about people who won't or can't use GitHub.
As far as I understand, this is purely a result of lack of maintainer resources. Apparently, nobody has been bothered enough by this to contribute the relevant changes. Keep in mind that all of rustc and libs development takes place on Github.
Re: Why stdx is not on crates.io
#26Re: Why stdx is not on crates.io
#27> Also, you can only create a crates.io account with a GitHub account Oh is that true? They tied themselves to Microsoft it seems. What about people who won't or can't use GitHub.
Yes, unfortunately it is true. Sad, but I could live with that. What in my opinion is unacceptable is that it requires you to give permission to "read your organization and team membership and private Projects" . I made a separate GitHub account (weinzierl-trusted-publisher) for crates.io which is far from ideal, because it works completely against the idea to build trust for a single unified identity online, but ¯\(…
Re: Why stdx is not on crates.io
#28Earlier quoted context omitted.
Yes, unfortunately it is true. Sad, but I could live with that. What in my opinion is unacceptable is that it requires you to give permission to "read your organization and team membership and private Projects" . I made a separate GitHub account (weinzierl-trusted-publisher) for crates.io which is far from ideal, because it works completely against the idea to build trust for a single unified identity online, but ¯\(…
Multiple free accounts are also against GitHub TOS
Re: Why stdx is not on crates.io
#29Earlier quoted context omitted.
Yes, unfortunately it is true. Sad, but I could live with that. What in my opinion is unacceptable is that it requires you to give permission to "read your organization and team membership and private Projects" . I made a separate GitHub account (weinzierl-trusted-publisher) for crates.io which is far from ideal, because it works completely against the idea to build trust for a single unified identity online, but ¯\(…
Multiple free accounts are also against GitHub TOS
Re: Why stdx is not on crates.io
#30"The solution to rust's supply chain woes is me stealing some code and vibe coding the rest" is truly one of the take of all time. And in general, people pointing at Rust "limited" stdlib (it's only limited compared to Python) as one of the big issue and risk with rust are, in my opinion, misguided. You will never make an stdlib big enough to remove the need for external dependencies. It also creates a bunch of other…