3 ms·
Cursor does this. And in my experience it gets it perfectly right 95% of the time or better. A lot of times I can start editing something and then just keep hit
by adastra22 1y ago
Cursor does this. And in my experience it gets it perfectly right 95% of the time or better. A lot of times I can start editing something and then just keep hitting tab over and over again until the change is complete--including jumping around the file to make edits in various disconnected places. Of course you can do most of this in Copilot too, but you'd expect something that maybe works and needs a lot of cleanup. The cursor autocomplete is, more often than not, EXACTLY what you would have hand crafted, without any deficiencies.
It's also somehow tracking what I look at, because I can look up an API and then return to the original source file and the first autocomplete suggestion is exactly what I was looking up, even though there would be no context to suggest it.
It's really quite magical, and a whole different level from Copilot.
- hu3 1y ago> Of course you can do most of this in Copilot too, but you'd expect something that maybe works and needs a lot of cleanup. That hasn't been my experience with Copilot next edit feature. It often understands exactly what I'm doing and I'm able to just tab tab around the file. Like my example about variable loop scope fixing. My experience is that Copilot does everything you said including considering files I viewed previously to better understand what I'm trying to do.
- adastra22 1y agoReading up on this, it sounds like Copilot adopted the methodology that Cursor has been using internally for more than a year. Which is great, but if your question is "why is everyone using Cursor?" it is because many initially used Cursor when they were the only ones with this feature. I, for example, specifically switched from Copilot on VSCode to Cursor because of the spooky accuracy of Cursor's tab complete compared to Copilot, at the time. This was only a few months ago.