In theory. The Treasury did just unsanction "Tornado Cash" a week ago which is basically built to anonymize crypto transactions by mixing up a bunch of them on the blockchain.
Money loves to be clean!

From my experience of onboarding people into production Rust code, I can't think of a time I've seen them lean into .unwrap(). They tend to overuse if let Some() and learn other ways to handle it later.
Footguns to me are silently waiting to be stopped on. unwrap is more of staring down the barrel

I'm not that familiar with Go, but to me the big thing isn't Option<&T>, but rather &T. If I'm writing a function it's more useful to me to be able to take a ref I know I don't have to check and can't be invalid without unsafe code.

Yep. TikTok and its partners like Oracle, and app stores like Apple & Google could be fined $5k per user still using the app in the US so there is incentive for them to ensure you can't access the app.

It's the same but also wildly different in exciting ways. I think @xblock.aendra.dev is my favorite thing to point to and to "isn't that cool??" if you haven't already seen it. Looking forward to what new creative ideas the new horde of users will come up with.

Fortunately they do have RSS feeds!
bsky.app/profile/did:...

*not github's BFG- Roberto's BFG :D
rewriting git history is hard, and remembering things is harder.

It likely isn't even deleted locally either, git tends to keep hashes around even if you removed them. git reflog has saved me many a time, but definitely worth checking GitHub's page about fully removing data from GitHub if you accidentally commit- tldr; git filter-repo or GitHub's BFG

Haven't had much issues with the syntax itself. Complex types can be pretty hard to read but aliases help a ton there.

I was surprised how much better Rust Analyzer was using Zed instead of VS Code along with Cranelift + Mold for faster builds. I totally didn't believe my coworker that claimed RA was better with neovim- but apparently VS Code LSP is kinda jank.