What are your issues with Cargo?
-
-
Replying to @whitequark @CopperheadOS and
Cargo is bloated everything-but-kitchen-sink. It introduces double chick-or-egg problem to Rust – you need cargo and rustc to build cargo and the same to build rustc.They don’t even provide static cargo for bootstrapping.Using git as pkgs index is horrible idea, it’s slow as hell
2 replies 1 retweet 2 likes -
Replying to @JakubJirutka @whitequark and
They made Cargo an inherent part of Rust, but it’s being developed as some hipster JS project.
2 replies 1 retweet 0 likes -
Replying to @JakubJirutka @RichFelker and
Cargo arrived after Rust, incremental improvement is totally a thing, and the distro package maintainer experience is understandably not the #1 priority. Try to be fair and kind.
2 replies 0 retweets 1 like -
Replying to @jdub @JakubJirutka and
Having an official package manager for a language is just bad policy. It's making the language into a product, not a language.
3 replies 1 retweet 2 likes -
Replying to @RichFelker @jdub and
Not every language has the luxury of being the official language of OS, like C on linux. I find package managers incredibly useful, because my community doesn't have the workpower to package every lib for every OS under the sun.
2 replies 0 retweets 2 likes -
You don't have to. Whoever is packaging apps for the dist will also package dependency libs or static link them, & devs can just grab & build the source for libs they want.
3 replies 0 retweets 0 likes -
Replying to @RichFelker @das_kube and
No, this is not how it works. Applications often have dozens or hundreds dependencies when we count transitive. It's totally insane and error prone to repackage them all, duplicate versions resolution etc.
1 reply 0 retweets 0 likes -
Replying to @JakubJirutka @das_kube and
Apps with that any deps are simply unfixably buggy. Even if a randomly chosen lib has 95% chance of being usably nonbuggy, 100 have < 1% chance.
3 replies 0 retweets 0 likes -
Replying to @RichFelker @JakubJirutka and
It's not like these probabilities are independent. Transitive dependencies should have a higher chance of being high quality, well-maintained libraries rather than a random github project. (I concede that it's different in some ecosystems, cough npm cough leftpad cough)
1 reply 0 retweets 1 like
That's a nice fantasy, but I'm pretty sure they're mostly independent. I've seen plenty of fairly good libs with glib as a dependency, because nobody looks under the hood to see how broken it is.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.