Optimize Concurrency: Why I Migrated from Python to Go

Optimize Concurrency: Why I Migrated from Python to GoOptimize Concurrency: Why I Migrated from Python to Go

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Jasper Rexford

pro

• 1d

So here's the number that made me move all my agents to Go.

A goroutine uses about 2kb of memory. An OS thread uses about 8mb. That's a 4000x difference per unit of work, and it's the whole reason my agents can run thousands of tasks at once on a single box instead of a fleet of them.

Where Python is fighting the GIL and falling over at a hundred concurrent scrapers, Go just spins up ten thousand goroutines and doesn't break a sweat. 10k tasks is like 20mb of memory instead of 80gb. The math isn't close.

Concurrency you can actually afford is concurrency you can ship.

Anyone else moved a workload off Python for this, or still making asyncio work?

aiautomation Claude aicoding

Boluwatife Delight

• 21h

This deserves more than just liking, this deserves to be featured! 🏆 That 4000x memory efficiency comparison is a crazy statistic. Optimizing backend task loads down to 2kb per unit while running thousands of concurrent tasks on a single box is incredible engineering.

Alex Prokhorov

max

• Jun 30

Claude Sonnet 5 is crazy efficient. One-shot this landing page and spent only 4% of 5h limit

Claude

Victor Adebayo

• Jun 30

Nice 👍

Lauri Lännenmäki

pro

• Jun 30

Not everything I build lives in Framer.

This one's a code project: I rebuilt Payy's React marketing site — a stablecoin payments company — from the front-end up. New typography system, a reusable motion foundation (scroll reveals, animated stats, page transitions), a handful of custom components, and a footer with proper parallax. All hand-written, no UI framework doing the heavy lifting.

I ran the whole build through Claude Code, which is where 15 years of front-end experience actually pays off — I'm not prompting and hoping. I know what good motion feels like, how to keep things performant and accessible, and where the real work is. The AI moves fast; the engineering judgment is mine. I also work fluently with MCPs like the Figma MCP, so I can pull straight from design files into clean, accurate code.

If you've got a Figma design that needs to become a real, performant site — in React, not just Framer — that's squarely my lane. Happy to talk through what you're building.

Check it out