Earlier quoted context omitted.
Tuist
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?
CocoaPods trunk read-only plan
81–90 of 116 posts
Re: CocoaPods trunk read-only plan
#82Finally!! I never liked CocoaPods due to how it “takes over” your Xcode project. I used to prefer Carthage, then just git submodules, then SPM. In my last job I oversaw SDK development and CocoaPods was the bain of my existence. Constant CDN problems causing release delays, annoying extra file in Ruby to maintain, different behavior than our other releases due to how CocoaPods builds projects, etc. SPM was as simple…
Finally someone sane.
Re: CocoaPods trunk read-only plan
#83The end of an era! Goodbye xcworkspace. For most of my use cases SPM is now much easier to use and causes less issues but a great effort from all the Cocoapods maintainers over the years. I wonder how interoperable SPM is though with non-Xcode build pipelines (e.g. Unity projects, ReactNative, Flutter, etc)?
React native support for SPM is non-existent for the most part. There's some work on porting to SPM but it's gonna be a while before anything becomes stable. It's going to break a huge amount of 3rd party packages. A bit of shame this wasn't done earlier as the RN ecosystem just went (or, is still going) through a migration to the "new architecture" that required most 3rd party packages that use native code to be "po…
React-Native is blocked by SwiftPM not supporting mixed ObjC and Swift packages. It needs that to support both the Old Architecture and the New Architecture at the same time.
Re: CocoaPods trunk read-only plan
#84Finally!! I never liked CocoaPods due to how it “takes over” your Xcode project. I used to prefer Carthage, then just git submodules, then SPM. In my last job I oversaw SDK development and CocoaPods was the bain of my existence. Constant CDN problems causing release delays, annoying extra file in Ruby to maintain, different behavior than our other releases due to how CocoaPods builds projects, etc. SPM was as simple…
I agree entirely. I feel like CocoaPods should have done this shortly after iOS 8 was released when dynamic frameworks were added. It was a terrible solution to a problem that way outlived its usefulness and because of that has absolutely polluted the ecosystem.
Re: CocoaPods trunk read-only plan
#85Earlier quoted context omitted.
It was not at all obvious to people that haven’t heard of tuist (presumably the intended audience of your post) that tuist is a product. I thought it was a typo or even possibly an insult (same form as racist, sexist, ableist, ageist, etc)
> I thought it was a typo or even possibly an insult (same form as racist, sexist, ableist, ageist, etc) That is on you, though.
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 to imply that there is some sort of "should" to this. The author is not required to want their meaning to be understood, even though I'm not really sure what other purpose they would have for posting. But I do think that this class of miscommunication is both common and reasonably avoidable by building up a bit of a mental model of the intended audience. I was trying to provide anecdotal evidence to build up that mental model.
Re: CocoaPods trunk read-only plan
#86Earlier quoted context omitted.
It was not at all obvious to people that haven’t heard of tuist (presumably the intended audience of your post) that tuist is a product. I thought it was a typo or even possibly an insult (same form as racist, sexist, ableist, ageist, etc)
> I thought it was a typo or even possibly an insult (same form as racist, sexist, ableist, ageist, etc) That is on you, though.
Another non-iOS developer here. It was absolutely not clear what you meant with a single word reply, and one that honestly looked like a typo or some kind of insult (short + -ist) I didn’t get.
Re: CocoaPods trunk read-only plan
#87Earlier quoted context omitted.
> I thought it was a typo or even possibly an insult (same form as racist, sexist, ableist, ageist, etc) That is on you, though.
Another non-iOS developer here. It was absolutely not clear what you meant with a single word reply, and one that honestly looked like a typo or some kind of insult (short + -ist) I didn’t get.
What I meant is that people who are non-ableist, non-racist, etc. do not have racism et al. popped up in their mind.
Why does everything have to do with those things in people's minds? It is tiring, and I am starting to believe they are the racists.
It never crossed my mind based on the name of a project. It is ridiculous.
Re: CocoaPods trunk read-only plan
#88Earlier quoted context omitted.
> I thought it was a typo or even possibly an insult (same form as racist, sexist, ableist, ageist, etc) That is on you, though.
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?
Re: CocoaPods trunk read-only plan
#89Earlier 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?
Because it was a single word ending in -ist, the common English suffix for a prejudice or preference? There was no context indicating that it was the name of a project.
Re: CocoaPods trunk read-only plan
#90Earlier quoted context omitted.
Yes, you can use SPM to package up Objective-C code.
Right, but you can’t have a single package containing both ObjC and Swift. It’s a limitation of SwiftPM that has prevented me from using it for a few projects (I am using it in several others, though).
You can mix them, it just has to be released as a binary framework which is a bit annoying as I would prefer a pure source release but it does work.