You must log in or register to comment.
This is a great little piece, although relevant to developing generally, not just Rust.
Who won? I think nobody really.
Good summary.
deleted by creator
I hate it when TLAs are not explained
From TFA (the fine article):
As for the title: a CDO is a financial instrument that became pretty infamous during the financial crisis of 2007. An entertaining explanation of that can be found in “The Big Short”.
Its the last sentence of the article as a footnote with a wikipedia link to a page about CDO.
and it doesn’t explain what the acronym stands for, or what it’s for
Uh, neither did you? Both explanations mostly just provide links.
well, I didn’t write the article
If you’re using an obscure acronym in your title, it deserves more than just a link in a footnote imo, but whatever
That’s fair.
deleted by creator
Credit Default Obligation?
Well written, I enjoyed this.
TIL rust has some sort of ratings for libraries/dependency code. Cool! Is that intrinsic in some way?
Speaking as a C/C++/python (and others) coder if that’s relevant, that’s been looking at Rust for a while…
I’m not sure, what they mean with those ratings, to be honest.
This whole article is about the
yaml-rustlibrary having been marked as unmaintained in the RUSTSEC advisory database: https://rustsec.org/packages/yaml-rust.htmlRUSTSEC is not intrinsic to the language, but it’s maintained by the Rust Foundation and there’s some really solid tooling, which can tell you in the blink of an eye that one of your dependencies is insecure.
Well, and then there’s some unofficial projects which curate libraries, like https://awesome-rust.com and https://lib.rs (the latter also serves as an alternative frontend for the official package registry https://crates.io ).
TIL rust has some sort of ratings for libraries/dependency code.
A random guy going through the trouble of putting together a site to subjectively rate other people’s work is hardly something that’s language-specific.
I’d wager that adding a single tag/field to represent the programming language is all it takes to make the system universal.
Also, that’s not even language-specific. It’s package-centric.
I get it, joining bandwagons is fun. That’s not a substitute for thinking things through, though.
By the way, npm even supports package auditing, warnings, and autopromoting packages and its dependencies. You don’t hear people constantly parroting switching projects to Node.js over this, though.
I think why really need a way to transfer ownership of crate names if the original owner is completely unresponsive. The Python ecosystem has a process for this.
tl;dr: They merged the code of an unmaintained dependency into their project.
I don’t think I can take anything else away from it.
Moooom, theyre treating the metric again!
