CocoaPods trunk read-only plan • Hacker News Board

Re: CocoaPods trunk read-only plan

#111

Post by josteink » Tue, Sep 02, 2025, 8:39 AM UTC

einsteinx2 wrote: post #92

josteink wrote: post #91

Earlier quoted context omitted.

Since it clearly wasn’t obvious, I was asking in the context of a package consumer, not publisher. My involvement with MacOS development is somewhat limited and I have no plans publishing any packages yet ;)

Oh gotcha, yeah they’re absolutely usable as any maintainer mixing the languages and providing SPM support will handle the binary release part. If anything it’s nicer for the consumer (binary releases in general) as it cuts down on full app rebuild times.

I kept hitting my head against the wall, and getting a million stupid errors trying to resolve header files. But in the end I got it working, and I will no longer be one of the guys pestering the old Cocoapods servers :)

For whoever comes after me... When ChatGPT suggests changing your Objective-C from this:

   #import package.h

To this:

   #import

Just skip that rabbithole of inifiny-nested failure, and just do this instead:

   @import package;

And you're done. You can thank me later :)

Re: CocoaPods trunk read-only plan

#112

Post by gregoriol » Tue, Sep 02, 2025, 9:12 AM UTC

kiliankoe wrote: post #94

gregoriol wrote: post #8

This is really sad, because the replacement, Swift Package Manager, is really crap: it lacks some useful features (an "outdated" command, meaningful commandline output, ...), is buggy as hell in xcode (most of the time xcode just crashes when you add/removed a dependency, error messages while getting a repository are not understandable and even often not visible entirely, many repositories have some old Package.swift…

If you're looking for an outdated command, maybe this works for you? https://github.com/kiliankoe/swift-outdated/ Disclaimer: I wrote this (a while back)

I'm using it, thanks so much for making it :-) It should have been part of the swift base tools, it is very useful.

Re: CocoaPods trunk read-only plan

#113

Post by kiliankoe » Tue, Sep 02, 2025, 10:19 AM UTC

gregoriol wrote: post #112

kiliankoe wrote: post #94

Earlier quoted context omitted.

If you're looking for an outdated command, maybe this works for you? https://github.com/kiliankoe/swift-outdated/ Disclaimer: I wrote this (a while back)

I'm using it, thanks so much for making it :-) It should have been part of the swift base tools, it is very useful.

Oh fantastic! And yes, I very much agree. I have some ideas for improving it a bit, maybe that'll make it worthwhile to PR into SwiftPM itself (:

Re: CocoaPods trunk read-only plan

#114

Post by tomaskafka » Tue, Sep 02, 2025, 11:10 AM UTC

gregoriol wrote: post #8

This is really sad, because the replacement, Swift Package Manager, is really crap: it lacks some useful features (an "outdated" command, meaningful commandline output, ...), is buggy as hell in xcode (most of the time xcode just crashes when you add/removed a dependency, error messages while getting a repository are not understandable and even often not visible entirely, many repositories have some old Package.swift…

Sounds like Microsoft’s “Embrace Extend Extinguish” approach that everyone hated (and some successfuly sued) has found a new home at Apple.

1 take over the thing 2 succeed at it as a platform owner 3 not put in resources to do it well

Re: CocoaPods trunk read-only plan

#115

Post by myko » Tue, Sep 02, 2025, 5:40 PM UTC

SoKamil wrote: post #81

myko wrote: post #34

Earlier quoted context omitted.

I will never start another Apple platform application without Tuist. If I start work on one I will do my best to get buy-in to switch.

Have you worked with Bazel before? Do you have a comparison to Tuist?

I haven't earnestly used Bazel but my limited experience with it is that it does work fairly well and if your project is multiplatform it might be a better choice than Tuist for the Apple specific pieces. But if your project is all Apple and you're deeply into the ecosystem Tuist would be my recommendation - instead of Bazel's DSL you just write Swift to describe your project.

Re: CocoaPods trunk read-only plan

#116

Post by adithyassekhar » Fri, Sep 05, 2025, 1:00 PM UTC

mrbombastic wrote: post #68

adithyassekhar wrote: post #56

Earlier quoted context omitted.

Why would you work for free for Facebook

rn is open source so I don’t personally see it as working for free for facebook but rather working for free for the dev community

There is no dev community. Is there a developers organization (unions if you must) which fights for minimum pay or work standards?

No there's not in fact it's actively frowned upon because if salaries are standardized no one will get to enjoy those huge faang pays. It'll be averages. That is not the capitalist way.

You're doing the work highly paid facebook and vercel employees are getting paid for.