Live data from Hacker News

Cursor 1.0

cursor.com

41–50 of 492 posts

Re: Cursor 1.0

#41

I love Cursor, but it feels like a ticking time bomb with extensions not being updated at the same rate as VSCode. Also another issue I am starting to see is the lack of shared MCP servers. If I have VSCode, Cursor, and Claude open, each one is running its own instance of the MCP server. You can imagine that with a dozen or so MCP's, the memory footprint becomes quite large for no reason.

Just run it on http

Re: Cursor 1.0

#42
post #7

VSCode with extensions Copilot [autocomplete] + CLINE [AI chat] + FOAM [obsidian-esk markdown support] is goat. There's no way a closed-source alternative to going to compete with this.

Have you given the alternatives a genuine test? My experience with Aider (never used Cline) is that it's nowhere near as good

The benefit of Aider is that you can configure a very involved static analysis toolchain to edits which directly triggers new edits in response, and everything is a git commit so it's easy to revert bad edits quickly. I have used both and I find Aider provides more control and produces code faster due to leaner prompts (it's also easier to run multiple Aider instances than Cursor instances), while Cursor has a prettier interface, and I do like being able to see diffs live in files (though I almost never spend the time reading them to accept/reject). I imagine if you don't spend any time configuring Aider cursor would probably seem far better.

Re: Cursor 1.0

#43
post #18

I love Cursor, but it feels like a ticking time bomb with extensions not being updated at the same rate as VSCode. Also another issue I am starting to see is the lack of shared MCP servers. If I have VSCode, Cursor, and Claude open, each one is running its own instance of the MCP server. You can imagine that with a dozen or so MCP's, the memory footprint becomes quite large for no reason.

That's why i use Docker MCP Catalog. One MCP Server to rule them all. more info: https://www.youtube.com/watch?v=6I2L4U7Xq6g

Here’s an alternate link if you prefer to read text instead of watching a 6 minute video: https://docs.docker.com/ai/mcp-catalog-and-toolkit/catalog/

Re: Cursor 1.0

#44

I love Cursor, but it feels like a ticking time bomb with extensions not being updated at the same rate as VSCode. Also another issue I am starting to see is the lack of shared MCP servers. If I have VSCode, Cursor, and Claude open, each one is running its own instance of the MCP server. You can imagine that with a dozen or so MCP's, the memory footprint becomes quite large for no reason.

It’s more of a ticking time bomb because it relies so heavily on upstream model providers who all have competing products, particularly Claude Code.

Re: Cursor 1.0

#45

I love Cursor, but it feels like a ticking time bomb with extensions not being updated at the same rate as VSCode. Also another issue I am starting to see is the lack of shared MCP servers. If I have VSCode, Cursor, and Claude open, each one is running its own instance of the MCP server. You can imagine that with a dozen or so MCP's, the memory footprint becomes quite large for no reason.

Just run it on http

this is the way.

STDIO MCP is really just a quick hack.

Re: Cursor 1.0

#46
post #18

I love Cursor, but it feels like a ticking time bomb with extensions not being updated at the same rate as VSCode. Also another issue I am starting to see is the lack of shared MCP servers. If I have VSCode, Cursor, and Claude open, each one is running its own instance of the MCP server. You can imagine that with a dozen or so MCP's, the memory footprint becomes quite large for no reason.

That's why i use Docker MCP Catalog. One MCP Server to rule them all. more info: https://www.youtube.com/watch?v=6I2L4U7Xq6g

I recently discovered toolhive which is pretty handy too https://github.com/stacklok/toolhive

Re: Cursor 1.0

#47
post #44

I love Cursor, but it feels like a ticking time bomb with extensions not being updated at the same rate as VSCode. Also another issue I am starting to see is the lack of shared MCP servers. If I have VSCode, Cursor, and Claude open, each one is running its own instance of the MCP server. You can imagine that with a dozen or so MCP's, the memory footprint becomes quite large for no reason.

It’s more of a ticking time bomb because it relies so heavily on upstream model providers who all have competing products, particularly Claude Code.

Until Claude Code becomes manageable price wise, I don’t think Cursor really sees them as their competition. I can burn the whole cursor subscription price in a single day with Claude Code.

Re: Cursor 1.0

#48
post #5

Cursor recently lost me as a customer. Too many updates that disturb my workflow and productivity, no easy way to roll back versions, super sparse changelogs, lots of magic in context building, really untransparent pricing on max mode. I recently made the switch to Claude Code on the Max plan and I couldn't be happier. The only real thing I'm missing is the diff view across files, but I assume it's just a matter of t…

> The only real thing I'm missing is the diff view across files

You can commit checkpoints prior to each major prompt and use any IDE’s builtin visual diff versus last commit. Then just rebase when the task is done

Re: Cursor 1.0

#49

Cursor had been atrocious. Building on top of an already crappy IDE, you’d hope that they are at least keeping up with VSCode improvements and updates. But they are far behind and instead keep slapping on more garbage. The agent stuff is largely useless. The tab prediction go nuts every few seconds completely disrupting flow.

Huh, I have the opposite experience. The only tab complete worth anything is in Cursor.

Re: Cursor 1.0

#50

Earlier quoted context omitted.

Have you given the alternatives a genuine test? My experience with Aider (never used Cline) is that it's nowhere near as good

The benefit of Aider is that you can configure a very involved static analysis toolchain to edits which directly triggers new edits in response, and everything is a git commit so it's easy to revert bad edits quickly. I have used both and I find Aider provides more control and produces code faster due to leaner prompts (it's also easier to run multiple Aider instances than Cursor instances), while Cursor has a pretti…

what are the most useful changes you've made to the configuration? This could be it - I haven't played with that a whole lot
Post reply on HN