@stroughtonsmith It looks like you're quickly progressing towards an eventual release. I think you're doing more than playing around at this point. haha

@stroughtonsmith Do you have experience with 3D applications? Or are you just vibe coding your way through this playing around? If it's the latter, i'm impressed. :)

@jsnell On the other hand, I 100% agreed with what you had to say on @gruber 's podcast. It feels gross, and like a money grab, and iWork should at least be part of the core macOS experience without all that.

@jsnell @gruber @daringfireball That makes it even more hilarious.

@leo The big difference I’ve noticed is Codex is better for developers who understand their code and want it to do specific tasks. Claude is better for describing what you want to see in the app and having it execute that.

@stroughtonsmith MarkEdit is a very nice app that does this. free on github.

@caseyliss As a non-developer myself asking it to make specific changes can address issues, but not underlying problems. I often have to ask it to re-examine a full function to find a fix. Additionally, it's really powerful for things like "Read the Apple HIG, and identify gaps in our application through a thorough audit of our code, then write those gaps to a file so we can systematically address the issues one at a time". This type of thing has blown my mind.