Limrun (@limrun) provides the infrastructure to leverage your favorite cloud agents for mobile development too. Today, we provide remote XCode, IOS & Android Simulators to Replit, Rork, Momentic AI, and many more. Congrats on the launch, @muvaff! ycombinator.com/launches/QSu…

A junior partner at a top vc told me he was worried i wasnt coachable. I said, i dont see what you can teach me given youve never founded or run a successful company.

The bottleneck for iOS dev is truly the CPU now. It's hard to work on features in parallel and testing if the app is compiled locally.

customers are increasingly asking us for certainty on capacity. as models get better, we expect that the world will be capacity-constrained for some time. we are offering discounted tokens for 1-3 year commits. (it also helps us plan, so hopefully a big win-win.)

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.

there will be a blog post about this. on what this means for bun, benchmarks, memory usage, maintainability going forward, and also the literal process of doing this (it wasn’t just “claude, rewrite bun in rust. make no mistakes”) this is a 960,000 LOC rewrite, the code truly works, passing the test suite on Linux and soon other platforms. e2e I started working on this 6 days ago. this would’ve been a massive amount of work by hand.

You know you're in the Bay Area when there are cracked-open laptops outside the bathroom running agents

this is what AUTOMATED UI testing looks like

The New Standard The way we build products has changed. It did not happen gradually. It became undeniable the week everyone came back from winter break and opened their laptops to find that the tools, the teammates, and the expectations had all quietly moved on. I call this "the new standard." Here is what I think has actually changed. Smaller Teams, Bigger Output We built the first version of Glaze, our second product, with three people in a couple of weeks. There are a few more on it now, but the pattern is what matters. Small groups are shipping things that used to need an entire org. Some of our designers are now among our top code committers. That sentence would have sounded absurd two years ago, and it is the clearest signal I have that something has shifted. The line between who builds and who describes what should be built has mostly dissolved. PMs are prototyping the features they used to spec. Engineers are making design decisions they would have punted to someone else. Everyone on a product team is a builder now, and the person closest to the problem is usually the one who solves it. A lot of that work never touches an IDE. It happens from a chat box, the browser, or a phone. Curation over Execution That is the upside. The downside is that when building gets cheap, everything gets built. More apps, more features, more dashboards, more surface area, more of everything. A lot of what I see shipped now is technically impressive and strategically pointless. The new constraint is not execution, it is curation. OpenAI is a useful example. They famously got distracted and did too many things at once. Now they are focused again, betting on one product and building it largely inside Codex. Just because something can be built does not mean it should be. The teams that win will be the ones that concentrate their effort, not the ones that spray it. The upside of this cheapness is real too. You can aim higher. Things that would have taken months are suddenly a few days. In the new version of Raycast, we shipped features we had discussed for years but never had the appetite to build. With AI, we could prototype them, see them come to life, and decide much faster whether they belonged in the product. Because deciding what should and shouldn’t belong is key here. The Debate Nobody has this figured out yet. Every team is rewriting its own playbook on the fly, and the playbooks rarely agree with each other. How small should a team actually be? What should it stop building? How do you keep quality high when shipping is cheap? We are starting an event series called The New Standard to sit down with teams I think get this right: Linear, Anthropic, Cursor, and Vercel. All companies known for restraint as much as for velocity. The first two are next week: 🌉 Monday, April 27, SF: The New Standard with @cursor_ai, @raycast, and @vercel (luma.com/egmieyv4) 🗽 Thursday, April 30, NYC: The New Standard with @linear, @raycast, and @AnthropicAI at @southpkcommons (luma.com/ldp71ob2) If there is a question you want me to put to them, send it in the replies. If your team has landed on a way of working that actually sticks, I want to hear about it. The standard for what a small group of people can build in a short amount of time has moved. Let's figure out together what it now demands of us.

Test your app on iOS and Android devices with one-click.

Introducing real iOS and Android device testing, right from your browser. If you've ever: 👉built a @Replit mobile app and had no way to test it on a phone 👉 been solely on Windows/Android and don't touch iOS …this is for you!

1. Go to an existing Replit project 2. “Make a mobile app” 3. Publish to App Store

You can now add a mobile app, slide deck, or animation to any web app you have built prior to Replit Agent 4. Everything lives in the same project, with shared branding & data. Just open your app and ask the Agent what you want to build. You also get $5 in credits to get started for a limited time

Big news: Rork raised a $15M seed round led by @leftlanecap with a16z @speedrun, @peakxvpartners, @trueventures, @GoodwaterCap, and others. Our team has been building mobile apps for the App Store since we were kids. Now we're making it possible for everyone else to do the same. And this is our story – in tribute to Howard Roark.

ANTHROPIC COMPLETES TENDER OFFER; SOME INVESTORS FALL SHORT AS EMPLOYEES HOLD ONTO SHARES

I made a new friend today