Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
Paul Berg
@prberg
Now that Copilot’s built into VSCode, why use Cursor at all?
6 replies
3 recasts
16 reactions
ɃΞrn
@b7
new copilot with mcp is fine for basic things. cursor & co is still far more configurable for adavanced stuff. and roocode just slaps!
0 reply
0 recast
1 reaction
woj
@woj.eth
probably will still miss some long tail features for a while but long term i agree, we will be back to regular vs code sooner or later
0 reply
0 recast
2 reactions
Gabriel Ayuso
@gabrielayuso.eth
This was my thinking over a year ago when I first heard about Cursor, that this integration would come and make Cursor less relevant but Cursor's feature set has consistently been better than Copilot's and they iterate much faster than Copilot. I haven't used Copilot in a whole though. It might be good enough. However I much rather switch to Zed than VSCode from Cursor.
0 reply
0 recast
0 reaction
dionysuz.eth
@dionysuz.eth
this but with zed agentic editing in beta: https://zed.dev/ai/agent
0 reply
0 recast
0 reaction
Carl Gustaf 👨🏼💻
@0xbob
To be frank I think Cursors features slaps harder, it feels great using it and I absolutely hated using copilot (haven’t tried since update) In the future I will probably move back to VS code but for now I think cursor works better.
0 reply
0 recast
0 reaction