You'd have to ban beets if you want to ban nitrates. Caffeine is more of a performance enhancer than nitrates, but they wouldn't ban it because everyone drinks coffee.
Sleep is the biggest performance enhancer. They should ban that.
The shoes definitely help, but there are all sorts of other innovations that get far less press.
More is known about optimal fuelling, hydration and sleep. Improve those and you improve your daily training. Better quality training compounds and allows you to reach closer to your talent ceiling.
Kerr also had a system set up so his bedroom had less oxygen than the rest of his house (to mimic sleeping at altitude).
He had two pacers breaking the air for the first 1,000m (although he had to do it himself the rest of the way, which was bloody impressive). Meant he could relax mentally for the first 2.5 laps and didn't have to focus on pace. I think El Guerrouj set the previous WR in a race without pacers.
They also had pacing lights on the track which helps the pacers run at an even pace.
And there are all sorts of innovations like taking sodium bicarbonate to reduce muscle acidity, nitrates to dilate the veins and increase blood flow to muscles and high doses of caffeine to reduce the rate of perceived exertion.
As someone else mentioned, track surfaces are generally a little bouncier now than they used to be.
Yeah, that's valid. It's not open source yet, but watch this space.
I can't even see people's email addresses when they sign up (as they just sign into their Claude Code account), but I get that you'd have to just take that on faith for now.
As it's a desktop app, someone can just point a proxy at it and watch exactly what it sends. You'll see that nothing like your conversations with Claude or even your login ever leave the app.
Yeah, I have used that and it's pretty good. For me, keeping up with multiple Claude Code agents got pretty annoying (hard to see which need your attention etc) so I felt like I needed a lightweight UI. I get that that isn't for everyone though.
VS Code with the extension uses Electron (heavy, because it bundles its own Chromium), extension host, and language servers which is what causes it to crash when you run multiple agents.
Abralo has a Rust backend (0% CPU) and has one shared webview (your native one).
But it's worth saying that the agents themselves use a huge amount of memory however you run them. That's why it's important not to layer additional overhead on top of each.
Is there any chance you could email me ([email protected]) with your OS and a little explanation of the bug (ideally with a screenshot)? Struggling to recreate it. Would be very grateful.
It already has created jobs where people just act as reviewers and gatekeepers though. There are people who vibecoded products and are now running decent-sized businesses.