@steipete @alex

I started a project recently and picked tuist. I had the same complaints about the files, so what I ended up doing is having all my code a in a single spam package that tuist depends on. I am basically using it solely for Xcode project generation, which removes the binary caching niceties.

I did end up writing a script to add all my spam targets into the workspace after generation, and I sometimes have to “save” the Paxkage.swift in Xcode if the project is regenerated, but I only need to regenerate if I add an new spm module.