Updating a Rust renderer from WGPU 24 to WGPU 30. 640 lines of fixes needed so far, and more to do. I've fixed all the easy stuff, and now I'm down to reverse engineering breaking changes of excessive cleverness.
I wonder if Claude Code could do this. That's a useful metric for the future - if a coding agent can't handle the breaking changes in a package upgrade, it's the package's fault. The day may come when that's something Github Actions checks for pull requests.
It's impressive that you didn't reach for Claude Code first :)
Would be good to keep track of how long it takes you to complete, so you can compare it with how long it takes Opus and then Fable to accomplish the same thing.
> It's impressive that you didn't reach for Claude Code first :)
I should have. All I have right now is a free Cursor account and Github Copilot. I've got to start spending money on tokens and get up to date. That article today by Carmack chewing out game devs for hand coding was striking, considering who he is and how much low level stuff he has done.
I'm doing 3D rendering in Rust. (Think three.js, but in Rust.) This is well outside the mainstream, so there's not much on the web to populate training sets. A year ago, AI coding tools could not cope with this area at all. Today, maybe.
I have no idea how good Claude is at understanding breaking changes to an API. I expect it would get simple changes, such as structure field renamings, without any trouble. But the gyrations required to handle write only access to GPU memory in Rust might not appear in the training data.