I have tried it now for the last few weeks. Finally disabled the feature in Xcode today.
No idea, this half-opaque suggestions all the time as soon as you start typing.
When I accepted the suggestions quickly, then I often had errors occurring later. Actually one would have checked everything carefully, what one accepts there. But that would already contradict the actual promise of being faster, using this stuff.
I’m not convinced, that it really is such a progress. It seems to me overhyped.
I don’t get the statements of many content-creators, that predictions increase your productivity so much.
Am I an exception or are there folks, who see it similar as me?
Would appreciate reading other’s opinion and experiences.
My opinion:
Sometimes it is useful, i.e. when writing common code such as an ForEach loop, it predicts my variable quite good and fills out all the standard text around the ForEach loop so that I can directly start with the content of the loop.
But most of the time it is simply stupid, as it predicts variable names but does not use the ones already defined. I give an example:
I’m writing an app which will display all money spent by a group. In my class, I have this variable defined as totalAmountSpentByGroup. When I start typing
Text("Money spent to date: \( it suggests totalAmountSpentToDate)" which is a variable nowhere defined. But it starts with totalAmountSpent which is clearly my writing and not a common variable name. So stupid.
1 Like
Yep. It tries to predict the name from the current surrounding. But it isn’t able to understand any context. It is, like you wrote: stupid.
1 Like
ehhhh mine works overall pretty good, and I haven’t had that experience you’ve had.
You can always try GitHub Copilot which is out now officially by GitHub and people have been saying it’s better than Apple’s right now
1 Like
Thanks. I know it from Visual Studio Code, which I use on work. But the Xcode-extension I haven’t known.
I disable it too. I don’t want to waste my brain.
1 Like