Originally posted in node /go/creative . Last edited by cursor at 2025-01-15 07:42 UTC+8.
Users share their custom rule files to force the AI to follow specific tech stacks (e.g., "Always use Tailwind CSS" or "Stick to TypeScript strict mode"). v2ex cursor
Users who are primarily backend engineers post about how Cursor helps them navigate complex React or Vue layouts that they previously found daunting. 4. Comparisons and Controversies Originally posted in node /go/creative
V2EX users are notoriously sensitive to platform lock-in. Discussions frequently warn against building a workflow entirely around Cursor. Since it is a proprietary fork, users fear "Orphaned Editor Syndrome"—if Cursor shuts down or changes pricing models, migrating extensions and settings back to standard VS Code or other forks (like VSCodium) could be difficult. This reflects a broader skepticism on V2EX regarding SaaS sustainability. Users who are primarily backend engineers post about
On V2EX, discussions regarding Cursor frequently begin with a sense of awe. Users often describe an initial "honeymoon phase" where the editor’s ability to predict multi-line edits and understand codebases feels akin to magic. A recurring theme in V2EX threads is the Unlike Copilot, which often relied on the immediate open tab, Cursor’s indexing of the entire local repository resonated deeply with V2EX users who manage complex, legacy codebases.