News for hackers. Stuff that matters.

A comment on The Next Chapter in Swift Build Technologies. Parent comment

Re:The Next Chapter in Swift Build Technologies by privacyis1mp on Saturday February 01, 2025 @06:13PM (#42903527)
Xcode gives me such a hard time that I started considering writing in Kotlin for macOS, just to have a normal IDE. We used to have AppCode (from JetBrains) and it was great. I wonder why Apple didn't support JetBrains, after all, it would have been to Apple's benefit.
[ Parent | on HN ]
Re:The Next Chapter in Swift Build Technologies by ChrisMarshallNY on Saturday February 01, 2025 @09:45PM (#42905182)
Personally, I never liked AppCode. It was too much like Eclipse (which I also never liked).

Me not liking something, does not make it bad. It’s just not my choice. I’m glad it existed, because it probably prompted Apple to do better with Xcode. Lots of people that I respect, used it.

These days, Xcode is Big Bug Ranch. When “Delete the DerivedData folder” is S. O. P. for developers, and Apple tweaked Xcode to reduce its impact on the project, you know that they have waved a white flag to bugs.

[ Parent | on HN ]
Re:The Next Chapter in Swift Build Technologies by joseda-hg on Saturday February 01, 2025 @10:08PM (#42905358)
There's even history of it working before, with Google / Kotlin
[ Parent | on HN ]