Member-only story
Not Dead Yet: Why C Still Fights, Rust Isn’t a Sure Thing, and AI Isn’t Magic
A peek under the hood of Cursor AI, a bold C upgrade that could stall Rust, how Curl stays battle-ready without a rewrite, a glimpse into how Claude “thinks,” and the strange new era where code is just another kind of content.
Not a Medium member you can read the article here for free
Everyone’s got hot takes on AI, Rust, and the future of code. So I pulled together a few that stood out — and added one of my own. Cursor’s doing clever stuff under the hood. Curl’s still shipping in pure C (and proud of it). TrapC is trying to save C from extinction. Claude’s doing its best to pretend it’s thinking. And meanwhile… code itself might just be turning into content.
Ever wonder how the Cursor AI code editor actually works under the hood? Roman Imankulov takes you on a behind-the-scenes tour, breaking down how it turns your vague coding requests into actual changes across your files. He digs into how Cursor structures its prompts, how you can shape its behavior with a simple config file, and how it smartly uses OpenAI’s function-calling to do things like search your codebase or edit files. It’s a solid peek into how modern AI dev tools really tick.
👉 Read the full post
C has taken a beating lately for not being memory safe — and Rust is gaining traction precisely because of that. To make matters worse, CISA is now pushing software vendors to move away from memory-unsafe languages altogether. Major tech players have already started backing Rust, rewriting parts of their system software in it.
Against this backdrop, Robin Rowe’s proposal for the TrapC extension to C is potentially game-changing. According to the proposal, compiling C code with a TrapC-aware compiler automatically upgrades all pointers to Memory Safe Pointers, with built-in checks and enhanced error handling mechanisms
Rowe asserts TrapC is on track to be released in 2025. If done well this can totally kill the C to Rust…
