I only use Swift for a side project, but I found myself splitting my time between AppCode and XCode. AppCode is nicer in terms of feature set (both in completeness and in my familiarity with the shortcuts), but I find XCode is <i>much</i> faster. If I'm working on something with a bunch of renaming/refactoring/etc, I'll do it in AppCode; if I'm more or less just typing and running tests, I'll do it in XCode.<p>So, while this announcement is sad, I can't say it's shocking. In other languages I know, IntelliJ products are significantly better than the competitors. For Swift, it's a bit more... meh.
AppCode i can understand, but the Swift plugin for CLion too? That's surprising, considering Apple is now maintaining a full featured LSP server implementation, so now VSCode users can do Swift dev<p>They have Fleet wich should support LSP, but i'm not sure if that product will be successful, they have a lot of work to do with regard to performance (cpu/memory), and based on the recent public preview, it's built with the wrong foundation for that matter
Oh, that's disappointing. I was wondering if anyone made a decent competitor to XCode after dipping my toes into some iOS development, and it looks like it's just being killed as I'm learning about it.
Shame to see it happen, but an understandable decision - it's been a few years since I was writing native iOS code and AppCode really felt like a power-user tool in ways that Xcode couldn't.<p>AppCode team, you did such a great job IMO
I believe that the greatest sorrow actually is that there will no more be copilot support for ios devs (except if you use vscode side-by-side with xcode).