Alex GrebenyukIt feels like the end of an era. I greatly respect everyone who created and then maintained CocoaPods for so many years.
David@a_grebenyuk In every iOS dev job I had so far CocoaPods was used as a dependency management system and overall it is a fantastic project and so criticial for a lot of apps. But since my current job requires the usage of RN and therefore CocoaPods I am ready for a change. Ruby tooling and the overall complexity of this tool while working with mostly web developers screams for a new modern approach. I really hope the RN project will migrate in the near future to something different.
@dvk it's a big question whether it's even feasible for RN right now since it's so entrenched in CocoaPods, and it uses a mix of C++, ObjC, and ObjC++. SwiftPM doesn't support mixed language targets, which has been a big hurdle in its adoption for some of my projects too.
@a_grebenyuk yes i know, Meta might even consider using their own tool BUCK to replace all of their CocoaPods infrastructure but as of now it doesn't seem likely CocoaPods will be replaced. Also there are so many 3rd party packages out there with a podspec already. I found ruby tooling (version, bundler gem) and cocoapods commands (install, update etc.) to be real hurdles for people not doing iOS development daily.
@dvk it is a hurdle for everyone lol
@a_grebenyuk 😁 well i don't disagree
@a_grebenyuk Even xcworkspace is sometimes troublesome... I can't count the # of times i had to ask whether the workspace or project was opened on a specific build issue at work.