USDC has a central issuer that can freeze funds because that's the only way you can currently have an asset that "looks like" dollars on a crypto ledger. Someone gets a dollar, mints a unit of the bearer token, and pinky swears they'll redeem it. It's a systemic concern that calls into question the legitimacy of the system, but that's not an oracle.

After a few rounds of this though it might end up seeming like it's not worth the hassle and it's easier to build the whole application in Rust.

And in this context, literally yes that's what it sounds like. The .ani file can contain multiple animation sequences that each have a name.

GHA was based on Azure Actions, which was never intended as a CI system nor meant to be used in a context where actions could be malicious. So it's the wrong tool for the job that had to be adapted to fit another use case, straying from its original design principles to make it work.

Which is why every library that wraps C APIs provides safe wrappers that express the implicit expectations within Rust's type system. Yes the low-level calls are unsafe, of course they are, but then we expose them with a safe interface that consumers actually use.

You do that by making the type system more sophisticated.

If you have a really important invariant that you really don't want to be violated due to run-time behavior/input, it's a huge benefit to have a compiler that can statically check that it actually can't be. That's one of the main benefits of having type systems, not just describing the shape of data structures in memory.