26 points

This is a great little piece, although relevant to developing generally, not just Rust.

Who won? I think nobody really.

Good summary.

permalink
report
reply
1 point
Deleted by creator
permalink
report
parent
reply
12 points
*

I hate it when TLAs are not explained

https://www.investopedia.com/terms/c/cdo.asp

permalink
report
reply
5 points

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.

permalink
report
parent
reply
3 points
*

and it doesn’t explain what the acronym stands for, or what it’s for

permalink
report
parent
reply
4 points

Uh, neither did you? Both explanations mostly just provide links.

permalink
report
parent
reply
2 points

Credit Default Obligation?

permalink
report
parent
reply
9 points

Well written, I enjoyed this.

permalink
report
reply
9 points

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…

permalink
report
reply
11 points

I’m not sure, what they mean with those ratings, to be honest.

This whole article is about the yaml-rust library having been marked as unmaintained in the RUSTSEC advisory database: https://rustsec.org/packages/yaml-rust.html

RUSTSEC 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 ).

permalink
report
parent
reply
-1 points
*

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.

permalink
report
parent
reply
6 points

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.

permalink
report
reply

Rust

!rust@programming.dev

Create post

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits
  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

Community stats

  • 598

    Monthly active users

  • 775

    Posts

  • 3.3K

    Comments