Can someone from the team share how the dev coordination for the Rust migration was handled? I only see a single PR (#9512)—how was the work organized?

There's some context here: https://news.ycombinator.com/item?id=38423908

This encapsulates the entire psychology behind every game ever created.

This is Awesome.

For my high school graduation project, I wrote a full COBOL system to automate soccer betting odds. Long past its prime, but my school hadn’t quite caught up with the times.

It was hilariously out of place, but I loved every line of it. There’s something oddly satisfying about a language that whispers, “Remember punched cards?” as you type.

It's really type resonant that you used COBOL (IN ALL CAPS) for your high school project. Makes for good high school memorabilia. I hope you used Greek gods for all of your variable names.

This is why doing long-term development on Android feels like trying to build a sandcastle during high tide.

Google forces you to use their ever-changing, drama-prone OS-level components through their “official” libraries. These libraries evolve faster than a teenager’s TikTok algorithm, so good luck keeping up. Oh, and if you don’t update your app to comply with their shiny new toolchains and runtime? The Play Store will ghost you faster than a bad Tinder match.

The alternative to "ask me clarifying question" is to use Claude's Projects. Upload all your projects' source code there, and ask Claude to do your programming task. OpenAI have recently also added this feature to their offering.

Give Claude a try when code generating, it works much better for my use cases.

worked 100% identifying my accent

The problem with sequential build/release number is that you have to keep it in git (so you could increment), which results in a number of complications and annoyances.

Am I the only one who thought this could alsop work lik "just" a find tool, only to discover it silently erased that word from all files in the directory without asking for confirmation? This felt riskier than rm -rf.

This should only happen if you hit enter on the confirmation screen - was it not clear that this would happen? I'd rather not slow users down by making them confirm that they definitely want to perform the replacement, but I'm happy to hear about other ways to make it clear that a replacement is going to be performed

Ouch. If you know Arabic or Hebrew, try selecting those languages and typing something in—it’s hilarious.

Looks like they’re “testing in production.”

The current deployed model is English only, we are rolling out a multilingual version later this week!

Oh. the UI lets you select fro various languages, so I assumed they should work. Thanks!