I have this crazy idea about agentic coding where you might want to prefer Rust over Python.
From my experience, the real struggle isn't writing code. It's understanding requirements clearly. To reach your main goal, you need answers to tons of questions. But more importantly, you first need to know which questions even exist.
This is where vibe coding breaks down.
You tell the LLM: "Hey, here's my great idea, code it up for me." It generates very performant code - a single file with thousands of lines (terrible) that will mostly work fine (the performant part).
But then problems appear. This feature? Don't want it like that. That other one? Don't want it at all. The vibe coded version becomes a compilation of suggestions for how your goal could be implemented, not what you actually need. And because it vibe coded everything together, you don't even want to read that code yourself.
Better approach: step by step coding.
You break things down. You become the manager. You can't just go do your own thing while the Agent codes. As the manager, you focus on the smaller steps needed to reach the final goal.
Here's the key: whether you use Rust or Python doesn't matter that much when you do small step coding. The Agent handles both languages well with this approach. So why not go directly with Rust?
Some very "smart" people might say "but library support..."
Yes, if you need PyTorch or specialized ML frameworks, use Python. But for many use cases, Rust gives you real benefits: lower CPU and RAM usage, no garbage collector, your app opens in milliseconds, it does its job multiple factors faster. Plus, for some goals, you want that low-level power.
And yes, you get to feel cool for using Rust.
#AgenticCoding #Rust #Python #AI #SoftwareDevelopment