I assure you, every inch of the interpreter code has been stared at by humans, a lot. TBH even the assembly generated by it has.
replyAll 150 kloc in six months by two people? Actually, it sounds like way too much code for the task unless 70+% of it is tests.
reply> By the end of the project, we wrote nearly four times as many lines of test code as we wrote for the Swift interpreter itself.
replyFrom what I got Apple is using claude code A LOT internally
replyIt would be interesting to see their internal guidance on LLM use. It’s a massive amount of new power that has to be wielded carefully. That kind of guidance might mean the survival or downfall of some big corps in the next few years.
replyYes they are using Claude Code - not the Xcode agents.
replyIt worries me. I hope Codex adoption picks up there.
thats a shame if true, they really should be dog-fooding that horrible agent ui in xcode to bring it up to a usable state
replyThe UI got a massive overhaul in the new Xcode beta. It’s no longer confined to the sidebar.
replyDevs continue to be tricked by incremental updates to it. It's still deficient
replyA lot of devs are tricked into using it because it’s official
replyI love how it doesn't even support reasoning output or edit tool diffs. (Yes it can show diffs sometimes when using the 100% official flow but not when using ACP)
replyIt also doesn't support Computer Use or Browser Use among other deficiencies
replySure but the basics should be down before tackling those, and they're not.
reply