Content
@
0 reply
0 recast
0 reaction
max
@maxp.eth
I’ve completely switched to cursor.sh, it’s what I imagined Copilot Chat should be. Now up to three AI subscriptions: - ChatGPT Plus - GitHub Copilot - Cursor Pro We’ll see who can innovate here faster. MS seems to be slipping behind.
16 replies
0 recast
36 reactions
billzh
@billzh
Same. Made the switch recently and it was really good. Interestingly I also have three subscription and am trying to see if I can consolidate. Was also trying Cody and using it to replace Copilot
1 reply
0 recast
1 reaction
Matt Solomon
@msolomon.eth
What do your workflows look like with cursor compared to just VSCode with copilot? Having the whole codebase indexed seems like the big benefit, but that seems mainly useful for asking questions about unfamiliar codebases (i.e. not sure how I’d leverage that feature, hence the workflow question)
1 reply
0 recast
0 reaction
billzh
@billzh
I was on VSCode + Copilot for a few months, but the biggest problem is that copilot doesn't have global context (i.e. not indexing the whole local database). Cody & Cursor have both solved that. Cursor also allows you to index latest docs for any library & quote code as context when submitting prompts
1 reply
0 recast
1 reaction
billzh
@billzh
I do think its killer use case today is to cut ramp up time for new libraries by 50%. Not very useful if you already know the library inside out
0 reply
0 recast
1 reaction