I bet these issues are caused by Swift though, because C, C++ and ObjC don't have those problems in Xcode (it's still far from perfect, but it's not slow or crashing).
Imagine an AppCode successor that was designed in full partnership with the XCode team? Tantalizing.
Or you just wanted to be dramatic?
No one wants that.
I'm sure Apple's Dev Tools team reads HN, and it's baffling they just don't care that the product has such a bad reputation. Or if the team cares, some layer of adjacent management clearly doesn't.
> or maybe even better, sizeable investment in them so they maintain autonomy and build a warchest to survive the current AI wave.
Just wow, like trying to talk to an LLM that poluted its context window with the wrong idea then hyperfixated on it ad infinitum, Jesus Christ.
> or maybe even better, sizeable investment in them so they maintain autonomy and build a warchest to survive the current AI wave.
Somehow harms Jetbrains.
Ideally they’d do what Google did with Android Studio. Of course Apple would never openly admit that their product is inferior to that of any of their competitors..
but please don't let that stop you from being the 4th comment to repeat itself.
The other part might be OK, but it's just too hard for me to imagine, I suppose. :-)