Javed A. Butt’s Post

I have this idea about agentic coding that might sound crazy: prefer Rust over Python. Here's my thinking. The real challenge in coding isn't writing the code itself. It's understanding requirements clearly. To reach your goal, you need answers to tons of questions. But first, you need to know which questions even exist. This is where vibe coding breaks down. You tell the LLM your great idea, and it generates very performant code. A single file with thousands of lines that mostly works fine. But then problems appear. This feature? Not 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 want to read that code yourself. Step by step coding works better. Instead of handing over your main goal, you break things down. You become the manager. You can't go do your own thing while the Agent codes. 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 much when you code in small steps. The Agent handles both well with this approach. So why not go directly with Rust? I know what's coming: "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 #SoftwareDevelopment

Me prefer golang and python to rustlang 'cuz me too dumb todo rust. Please write a rust translation tool: rust <--> go and rust <--> python ... would be useful and informative. Perhaps it would persuade more folks to consider rust despite its current lack of (shrinking) interest in the commnity.

Like
Reply

To view or add a comment, sign in

Explore content categories