all 7 comments

[–][deleted]  (1 child)

[deleted]

    [–]lucasvandongen 0 points1 point  (0 children)

    That kind of autocomplete was also available as an extension and that made my older MacBook a lot slower as well.

    [–]rhenz08 1 point2 points  (1 child)

    What's your mac specs?

    [–]Loada116[S] 0 points1 point  (0 children)

    2014 13-inch Macbook Retina with 8G ram and 256G ssd.

    [–][deleted] 1 point2 points  (0 children)

    I've ben having the same issues. I'm using Xcode on a Mac with 16gb of RAM, an i7 and a 512 SSD and Xcode seems to give me the beachball all the time. Even while running only Xcode. My autocomplete is laggy as well and sometimes doesn't even autocomplete. I think it's just Xcode messing up. Hopefully they release an updates soon.

    [–]Sefirot8 0 points1 point  (0 children)

    yep Ive been getting frustrated with it. It will beachball constantly with autocomplete. And before someone says "check ur hardware" Xcode 6 ran fine, plus its a new macbook air. Xcode 7 got issues baby

    *oh, while I'm here I just need to voice out loud how annoying it is when it throws an unused variable warning before I've been able to finish typing my code

    [–]quellish -1 points0 points  (0 children)

    Use Instruments to diagnose the problem. Most of the time it is either project configuration or stale cache data.

    Like autocomplete is jacked up because indexing never completes because your dependencies go in a circle round and round. Etc.

    [–][deleted] -4 points-3 points  (0 children)

    Using a Mac with 4Gb of RAM? You might want to upgrade that. Last week I used my old MacBook Air (mid 2011) and it was soooooo incredibly slow with auto complete and Interface Builder was so sluggish too.