GitHub Copilot is too fast #122181
Replies: 1 comment
-
I also find the increased eagerness problematic. It triggers lag in the VSCode UI which is distracting and unpleasant. To be a little more constructive, it would be great if we could have a configurable delay before inline completion triggered. There's already discussions about the "Copilot Pause" (when developers using Copilot will pause for a moment after typing some code, waiting for Copilot to complete it), letting us double-down on this effect as an intended usage pattern would be very helpful. I'm sure that I and many others have an instinct for the types of prefixes that work well for Copilot for us, we know how fast we type too, and so can dial in how long of a pause should be required to trigger completions. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
Copilot used to be slower, meaning that it wasn't as annoying when writing code. However, with recent updates it suggests code a lot faster, making it nearly impossible to ignored the code at times, and it will continue suggesting when the user types.
Worst of all, is that these suggestions are utterly useless, mostly incorrect and often just make the workflow longer. For this reason I've decided to stop using Copilot, because it ends up slowing me down, rather than helping in any meaningful way.
Beta Was this translation helpful? Give feedback.
All reactions