Live data from Hacker News

CocoaPods trunk read-only plan

blog.cocoapods.org

101–110 of 116 posts

Re: CocoaPods trunk read-only plan

#101
post #64

The interesting question is what happens to the ~100k+ pods that never migrated to SPM. There's probably a lot of useful but abandoned code that smaller projects still depend on. This creates a bifurcation where legacy projects get stuck on older toolchains.

  > The interesting question is what happens to the ~100k+ pods that never migrated to SPM.
from experience in a few projects that migrated to spm: fork and port to spm (at the same time, mark them as deprecated and slowly wean off them)

  > abandoned code that smaller projects still depend on
there are alot of large commercial projects too that are in the same boat...

Re: CocoaPods trunk read-only plan

#102
post #17
post #10

Doesn't React Native depend on this very heavily for iOS?

Yeah, and according to https://expo.dev/blog/precompiled-react-native-for-ios and linked https://github.com/react-native-community/discussions-and-pr... , it seems moving off CocoaPods has barely moved past planning stage. Latest update from two weeks ago links to https://github.com/facebook/react-native/pull/52909 and says it’s very very experimental. Just great…

It's not actually that concerning. RN's pods are vended via npm not trunk so trunk going read-only will not have an outsized impact on RN.

The risk is that over time Cocoapods will no longer work to integrate dependencies with ways Xcode wants them to be.

Switching to SPM is a massive undertaking for a large project with many intertwined dependencies and configuration options. It's far less configurable than Cocoapods with basically no scripting options during install.

Their progress already is pretty decent!

Re: CocoaPods trunk read-only plan

#103
post #96

Earlier quoted context omitted.

If you’re not familiar with the experience of browsing the internet and then suddenly having deeply-held parts of your identity deemed undeserving of respect, it’s the kind of thing that the mind naturally develops habits to avoid, in much the same way that you might start to walk differently through a city after getting mugged. It is indeed tiring for everyone, but the solution is not to blame people for doing what…

Of course I do, but we are talking about a project's name.

That’s the whole point. If you know we are talking about a project name (for instance by using the word in a sentence) then it makes perfect sense, but with no context one is left to try to use etymology like one might do with any unknown word.

Re: CocoaPods trunk read-only plan

#104

Earlier quoted context omitted.

I completely agree with you that if I had wanted to I could have put in the effort to decipher the meaning of the post. However, the post left me with absolutely no desire to decipher it's meaning, so I did not. If instead the author had written simply "I use tuist for that" the meaning would have been immediately clear for someone like me, and I would have been much more likely to look up the product. I don't mean t…

We are talking about a project's name. Why did racism (and friends) came up in your mind, or an insult? Why is this the default norm, now? People are free to down-vote me, but they cannot deny there is no truth to what I am saying. I would have never thought that a project's name was intended to be racist or cause any sort of harm. Why did you?

> We are talking about a project's name. Why did racism (and friends) came up in your mind, or an insult?

Please don’t take what I said as any kind of allegation that you were being insulting. Those associations were from trying to parse the word as English, which resulted in some unknown word from the family of words relating to prejudice presumably relating to textual user interfaces vs graphical. Context would have made it clear that it was a project name, in which case the word doesn’t need to be parsed.

Re: CocoaPods trunk read-only plan

#105
post #17

Earlier quoted context omitted.

Yeah, and according to https://expo.dev/blog/precompiled-react-native-for-ios and linked https://github.com/react-native-community/discussions-and-pr... , it seems moving off CocoaPods has barely moved past planning stage. Latest update from two weeks ago links to https://github.com/facebook/react-native/pull/52909 and says it’s very very experimental. Just great…

It's not actually that concerning. RN's pods are vended via npm not trunk so trunk going read-only will not have an outsized impact on RN. The risk is that over time Cocoapods will no longer work to integrate dependencies with ways Xcode wants them to be. Switching to SPM is a massive undertaking for a large project with many intertwined dependencies and configuration options. It's far less configurable than Cocoapod…

I think the most concerning part is all the third party libraries already on life support or already abandoned a few years ago will all die during the switch.

Re: CocoaPods trunk read-only plan

#106
post #66
post #51

Earlier quoted context omitted.

Open source superior just means newer, even if it comes with less features and more bugs

OP here, luckily in this case, it means a more supported and vertically integrated alternative. Which does have less features, but actually gets bugs fixed and keeps up to date with the platform - so it's a net win overall IMO

Thanks, your work was of huge value to me, way more than you were rewarded for, sorry :/

Re: CocoaPods trunk read-only plan

#107

Earlier quoted context omitted.

Local Swift packages are indeed improving the experience a little bit: better version management, less xcode crashes, slightly more explicit errors, but still highly troublesome. It really feels like Apple's teams are not using any of SwiftPM themselves.

> It really feels like Apple's teams are not using any of SwiftPM themselves. They probably never will, at least not for anything that ships with the OS. For Apple, binary size is very important, and it’s essential that they have only one of every library (“project”) installed on the device, and that they use dynamic linking everywhere. SwiftPM uses static linking to the core, and if Apple were to use it, binary size…

[deleted]

Re: CocoaPods trunk read-only plan

#108

Isnt this a old news? I'm thinking of Swift Package manager for all the stuff new.

From my experience, about 20-30% of the packages are not working with swiftpm, either because they don't have a Package.swift file, or because it is not compatible with up-to-date developer tools. On many projects, I had to fork a few repositories just to add or fix the swiftpm integration... while their Pod integration has always been working well.

I‘d say it’s 2% now, of the maintained ones? I haven’t seen such a project in a long while now. React Native is the only one I can think of.

Re: CocoaPods trunk read-only plan

#109

Earlier quoted context omitted.

Of course I do, but we are talking about a project's name.

That’s the whole point. If you know we are talking about a project name (for instance by using the word in a sentence) then it makes perfect sense, but with no context one is left to try to use etymology like one might do with any unknown word.

So you admit to it being an unknown word.

I did not, for a second, think, that an unknown word was intended to be racist, ableist, etc.

Why would you?

Also parent's reply:

> If you’re not familiar with the experience of browsing the internet and then suddenly having deeply-held parts of your identity deemed undeserving of respect [...] the solution is not to blame people for doing what they feel like they need to do to protect themselves.

It was a comment under a submission, FWIW.

Seriously though, just stop assuming everything is about race and friends. It is what is tiring. Ask first before making assumptions if it really is not a slur you know of, but an UNKNOWN WORD. If he were to say n***e* then yeah, have at it. That cannot be misunderstood.

And by my reply "That is on you" is down-voted for fuck-all, because people does not realize that the people preoccupied with racism are the ones first to believe it was a racist slur. I did not think it was a racist slur, because 1) it was an unknown word, 2) I am not preoccupied with such stuff, my mind is not filled with racism and such. Thus, the people who say "racist!" usually turn out to be the racists. I have seen it everywhere. Now I saw it on HN, too, which is just splendid. A single search would have sufficed. I do not deny that the person saying the word could have clarified what it is, but defaulting to believing it has to do with racism is one of the reasons for why we have racism. It did not cross my mind. Why did it cross yours, especially if you knew nothing but the unknown word?

I do not see race. Am I the racist one or the people thinking everything is about racism? Do not worry, I see race when it comes to a groups of people, except in that case it does not matter much, a group of people may always be trouble, regardless of race, so no, I did not abandon my self-preservation.

There is a lot to unpack here, my bad.

Re: CocoaPods trunk read-only plan

#110

Earlier quoted context omitted.

We are talking about a project's name. Why did racism (and friends) came up in your mind, or an insult? Why is this the default norm, now? People are free to down-vote me, but they cannot deny there is no truth to what I am saying. I would have never thought that a project's name was intended to be racist or cause any sort of harm. Why did you?

> We are talking about a project's name. Why did racism (and friends) came up in your mind, or an insult? Please don’t take what I said as any kind of allegation that you were being insulting. Those associations were from trying to parse the word as English, which resulted in some unknown word from the family of words relating to prejudice presumably relating to textual user interfaces vs graphical. Context would hav…

It was not me who said the word, FWIW.
Post reply on HN