[lapcat]

It's condescension because you continue to refuse to believe what I'm saying, and you keep insisting that something difficult is easy.

Moreover, if I needed help with a Swift issue, I would go to my many friends and associates in the Apple developer community. In fact, I've discussed the issue with some members of the Apple Swift engineering team, and I have an open bug report that Apple hasn't addressed. The very last person in the world I would consult about a programming issue is a random, condescending HN replier.

[Grustaf]

I don't doubt that you find it difficult, I am just saying that I never had any problems migrating to Swift 5. That's why I offered help, and because I am genuinely curious what it was that you found so overwhelming.

[lapcat]

> I don't doubt that you find it difficult

Wow, you just won't stop with the condescension. You won't even accept that it is difficult.

> I am just saying that I never had any problems migrating to Swift 5.

Good for you. Guess what, people have different code and different experiences.

> you found so overwhelming

I didn't say it was "overwhelming". I said that it's more trouble than it's worth for a free hobby project. It's not even a real problem yet, because as I already said, "The project now compiles". The problem will occur "when Swift 4 support is removed from Xcode", which hasn't happened yet. Even when that does happen, I can keep around an older copy of Xcode for quite some time.

The reason I brought this up in the first place is that unlike with Swift, I can still compile very old Objective-C code, and sometimes I need to. Objective-C generally doesn't break stuff (with the notable exception of Objective-C Garbage Collection). I'd rather not deal with the hassle of tool breakage if I don't need to.

[Grustaf]

That's because Objective C is too old for anyone to bother improving it. That doesn't seem like a positive.