5 ms·

I really wish Apple would focus more on getting Xcode up to par. It's in a truly horrid state, both performance and feature-wise. Developing an Objective-C app

I really wish Apple would focus more on getting Xcode up to par. It's in a truly horrid state, both performance and feature-wise. Developing an Objective-C app is worlds ahead of Swift right now.

hellofunk 9y ago
Are you aware that Xcode 9 just shipped last week and is a major rewrite of much of the IDE? It's one of the largest updates in Xcode's history.
- pavlov 9y ago
  Sounds like a great reason to stick with v8 for at least six months.
- sho_hn 9y ago
  So ... any good?
  - dep_b 9y ago
    The only that truly annoyed me was that CMD+click doesn't work immediately anymore but conjures some kind of intermediary menu. Haven't figured out if there's a new keystroke for it, but I'm still doing too much work in Xcode 8. To me it was nothing but progress compared to 8 apart from that. Everything faster and better.
    - jclardy 9y ago
      There is a checkbox in Xcode preferences to change it back. Not sure where as I’m on mobile, but that annoyed me to no end till I found the option. I agree on faster and better, but still buggy. Autocomplete still regularly dies for me and requires a restart (of Xcode.)
      - rockshassa 9y ago
        Preferences > Navigation > "Command Click on Code"
    - nnd 9y ago
      It's CMD+Control
    - nteunh34nteu 9y ago
      The new key command for it is right there in the menu when it pops up. If you select the first item to do what the old command did, it's literally just to the right of the command!
      - dep_b 9y ago
        Yeah....but muscle memory....
  - hellofunk 9y ago
    I haven't used it much yet myself, but I did notice that one annoyance I had was fixed, regarding zooming the font onscreen.
  - sgt 9y ago
    I've used it for a couple of days now. I've seen some issues with the Simulator but I think that's not strictly related to the IDE. As far as Xcode and the editor is concerned - it's extremely quick now. Functionally also better in terms of the code editor.
- deleted 9y ago
  [deleted]
- nodamage 9y ago
  Xcode 9 has been a lot less stable for me compared to previous versions. It will lock-up multiple times per day during simple text editing tasks, with SourceKitService going bananas until I force quit it.
  - indemnity 9y ago
    It boggles the mind that they just can’t seem to fix SourceKitService for three versions now, it’s such a massive part of making the Xcode experience suck. It’s worse than no completion, you never know when it’s actually going to work. I guess it does do something though, for eating up all those cycles.
    - imron 9y ago
      > it’s such a massive part of making the Xcode experience suck. This. Whenever my fans start spinning up, I head on over to Activity Monitor and sure enough SourceKitService is sitting at 120% CPU draining battery like nothing else. I probably kill the service between 5-10 times a day when using Xcode. I've found that disabling 'live issues' in preferences helps somewhat, at the expense of not getting live updates to errors as I'm typing, but SourceKitService will still go off the deepend - usually while adding stuff that will not yet compile because I haven't included the appropriate headers yet or am still refactoring/moving about code.
- ramensea 9y ago
  XCode 9 is unsurprisingly terrible for me. Between it and the Swift tool chain, they use over 10 gbs of memory and constantly using 100% of my CPU. XCode 9 seems like an improvement over 8 in some cases, but its way less stable, uses an insane amount of resources, and crashes more often.
  - mmargerum 9y ago
    It’s been so bad that I actually installed Jetbrains AppCode. It’s working great . I finally just bought the entire subscription since I already use IntelliJ, datagrip, gogland, and webstorm

I really wish Apple would focus more on getting Xcode up to par. It's in a truly horrid state, both performance and feature-wise. Developing an Objective-C app is worlds ahead of Swift right now.

hellofunk 9y ago

Are you aware that Xcode 9 just shipped last week and is a major rewrite of much of the IDE? It's one of the largest updates in Xcode's history.

pavlov 9y ago
Sounds like a great reason to stick with v8 for at least six months.
sho_hn 9y ago
So ... any good?
- dep_b 9y ago
  The only that truly annoyed me was that CMD+click doesn't work immediately anymore but conjures some kind of intermediary menu. Haven't figured out if there's a new keystroke for it, but I'm still doing too much work in Xcode 8. To me it was nothing but progress compared to 8 apart from that. Everything faster and better.
  - jclardy 9y ago
    There is a checkbox in Xcode preferences to change it back. Not sure where as I’m on mobile, but that annoyed me to no end till I found the option. I agree on faster and better, but still buggy. Autocomplete still regularly dies for me and requires a restart (of Xcode.)
    - rockshassa 9y ago
      Preferences > Navigation > "Command Click on Code"
  - nnd 9y ago
    It's CMD+Control
  - nteunh34nteu 9y ago
    The new key command for it is right there in the menu when it pops up. If you select the first item to do what the old command did, it's literally just to the right of the command!
    - dep_b 9y ago
      Yeah....but muscle memory....
- hellofunk 9y ago
  I haven't used it much yet myself, but I did notice that one annoyance I had was fixed, regarding zooming the font onscreen.
- sgt 9y ago
  I've used it for a couple of days now. I've seen some issues with the Simulator but I think that's not strictly related to the IDE. As far as Xcode and the editor is concerned - it's extremely quick now. Functionally also better in terms of the code editor.
deleted 9y ago
[deleted]
nodamage 9y ago
Xcode 9 has been a lot less stable for me compared to previous versions. It will lock-up multiple times per day during simple text editing tasks, with SourceKitService going bananas until I force quit it.
- indemnity 9y ago
  It boggles the mind that they just can’t seem to fix SourceKitService for three versions now, it’s such a massive part of making the Xcode experience suck. It’s worse than no completion, you never know when it’s actually going to work. I guess it does do something though, for eating up all those cycles.
  - imron 9y ago
    > it’s such a massive part of making the Xcode experience suck. This. Whenever my fans start spinning up, I head on over to Activity Monitor and sure enough SourceKitService is sitting at 120% CPU draining battery like nothing else. I probably kill the service between 5-10 times a day when using Xcode. I've found that disabling 'live issues' in preferences helps somewhat, at the expense of not getting live updates to errors as I'm typing, but SourceKitService will still go off the deepend - usually while adding stuff that will not yet compile because I haven't included the appropriate headers yet or am still refactoring/moving about code.
ramensea 9y ago
XCode 9 is unsurprisingly terrible for me. Between it and the Swift tool chain, they use over 10 gbs of memory and constantly using 100% of my CPU. XCode 9 seems like an improvement over 8 in some cases, but its way less stable, uses an insane amount of resources, and crashes more often.
- mmargerum 9y ago
  It’s been so bad that I actually installed Jetbrains AppCode. It’s working great . I finally just bought the entire subscription since I already use IntelliJ, datagrip, gogland, and webstorm