|
|
|
|
|
by lolinder
493 days ago
|
|
I tried it last month on a medium size personal project and was blown away by the autocomplete. I'd previously staunchly refused to try it on the grounds that I'm too productive in IntelliJ, but at this point I'm most likely going to start paying for both. I don't know if I'm ready to use it as a daily driver, but there are certain kinds of tasks—especially large refactors—where its ability to rapidly suggest and accurately make the changes across a file is incredibly valuable. It somehow manages to do all of that without ever breaking my sense of flow, which is more than I can say for Copilot's suggestions. And yeah, I'm with you that autocomplete is the way to go. I think chat is a red herring that will have long-term negative effects if it's used extensively in a codebase. Autocomplete keeps you in touch with the code while still benefiting from the co-pilot, and Cursor's UX for that is far and away the best I've seen. |
|