W1siziisijiwmtuvmdivmtivmtyvmzyvmdqvnteyl0f2yxrhci5wbmcixsxbinailcj0ahvtyiisijmwmhgzmdajil1d?sha=40d429a2ffd553af
Can someone explain why Cocoapods uses this stupid Podspec system?! All it does is being a half assed attempt at creating an alternative to an Xcode project, which I still have to maintain side by ...

Can someone explain why Cocoapods uses this stupid Podspec system?! All it does is being a half assed attempt at creating an alternative to an Xcode project, which I still have to maintain side by side with the podspec. And I have to resort to stupid hacks to get include paths preserved with their folders, because by itself this isn’t supported in Cocoapods. My Xcode projects builds a nice library, it copies all include files into the right destination, why the fuck doesn’t Cocoapods take an Xcode project and a target name and compile that?! Why does it have to do this bullshit “look, I invented my own fancy project file format” dance.

The more I work with it, the more I dislike Cocoapods and its architecture.

This document is webmention enabled.