You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not familiar with SPM. I haven't used it yet. Do you see practical benefits to switching from cocoapods to SPM?
One thing to consider is that we don't update dependencies often, and we try hard not to add new ones. This is to support our goal for the app to be as performant and lightweight as possible. Another thing to consider is that we commit dependency on git, so cocoapods is not used for people git clone'ing the project. It's only used to download new dependencies on rare occasion.
What do you think? Still worth a shot? Maybe it bundles dependencies in a way which improves performance?
I worry a bit about some of our dependencies which use a fork of popular repos, so we could use our patches. That may be tricky to move to SPM.
Do you see practical benefits to switching from cocoapods to SPM?
I do not remember a single time when I cloned a repo using cocoapods and managed to get it to build on the first try or even within like 10 minutes. With SPM that is a pretty common experience. But I did not realize that you do not use cocoapods to pull in the dependencies.
None of the things that you mention should be a show stopper tho. But the whole build process would be simple with SPM.
Is there interest in migrating the project to SwiftPM? If yes, I'm willing to fix it.
The text was updated successfully, but these errors were encountered: