Earlier quoted context omitted.
> Can cursor even do anything that vscode can't right now? Right now VSCode can do things that Cursor cannot, but mostly because of the market place. If Cursor invests money into the actual IDE part of the product I can see them eclipsing Microsoft at the game. They definitely have the momentum. But at least some of the folks I follow on Twitter that were die-hard Cursor users have moved back to VSCode for a variety…
How is Microsoft mismanaging things?
Graphite is joining Cursor
251–260 of 264 posts
Re: Graphite is joining Cursor
#252Well, time to bite the bullet and learn jujutsu over the holidays
Re: Graphite is joining Cursor
#253Re: Graphite is joining Cursor
#254Earlier quoted context omitted.
Part of a healthy codebase is ensuring that anyone can hack on it, regardless of their editor setup. Relying on something in .vscode and just assuming people are using that editor is what leads to this kind of situation. Bake that into the workflow some other way.
Or just enforce that the team all uses the same tools, and you save quite a lot in productivity between making things work on different tools, more so than whatever productivity gains individual devs on the team get from using their own preferred tools. Many teams I know issue everyone MacBooks and enforce VSCode usage, for example, and that has saved so much time compared to other teams I've seen where devs can choo…
Re: Graphite is joining Cursor
#255Earlier quoted context omitted.
Or just enforce that the team all uses the same tools, and you save quite a lot in productivity between making things work on different tools, more so than whatever productivity gains individual devs on the team get from using their own preferred tools. Many teams I know issue everyone MacBooks and enforce VSCode usage, for example, and that has saved so much time compared to other teams I've seen where devs can choo…
Saves so much time??? Really? You set up a dev env once, how much time is it even possible to save?
Re: Graphite is joining Cursor
#256Earlier quoted context omitted.
Strawman. Imaginary situation: People are using claude instead of cursor, and you can run claude in a terminal, so this is going back to the days of not using an IDE for the people that do it. Straw man shake down: Terminal based development like vim and emacs are old and shit, and we moved away from that for a reason, and so (although totally unrelated) this means 'using claude' means going back to using a terminal…
Lets see how that holds in five years time. I am betting it won't. By the way, there are OS APIs, I am yet to write a CLI driven agent, as part of iPaaS deployments, which are basically SaaS IDEs. vi and Emacs are certainly not IDEs, they are programmer editors, although with enough effort they may pretend to be one.
That being said, surely the point here is about "agent driven development" vs "ai autocomplete". As they say, whether you type your command into a web window or a terminal window presumably doesn't change the flow that much.
Re: Graphite is joining Cursor
#257Earlier quoted context omitted.
Apples and oranges comparison. I don’t think it’s the same and good for you for waiting on Opus to respond. I don’t have the energy.
> Waiting for Opus Sir Opus is the fast one of the bunch. Try GPT 5.2 high.
Re: Graphite is joining Cursor
#258Earlier quoted context omitted.
Heard on the worry, but I can confirm Graphite isn’t going anywhere. We're doubling down on building the best workflow, now with more resourcing than ever before!
Supermaven said the same thing when they were acquired by Cursor and then EOLed a year later. Honestly, it makes sense to me that Cursor would shut down products it acquires - I just dislike pretending that something else is happening.
Re: Graphite is joining Cursor
#259Imo Cursor did had the first mover advantage by making the first well known AI coding agent IDE. But I can't help but think they have no realistic path forward. As someone who is a huge IDE fan, I vastly prefer the experience from Codex CLI compared to having that built into my IDE, which I customize for my general purposes. The fact it's a fork of VSCode (or whatever) will make me never use it. I wonder if they bet…
Are you sure entire opinion is not just centred around that fact? Sounds like it
The UX of IDE integration with the existing VSCode plugins and file manager… it’s not even close to the same. Some people just get comfortable with what they are comfortable with
Re: Graphite is joining Cursor
#260Imo Cursor did had the first mover advantage by making the first well known AI coding agent IDE. But I can't help but think they have no realistic path forward. As someone who is a huge IDE fan, I vastly prefer the experience from Codex CLI compared to having that built into my IDE, which I customize for my general purposes. The fact it's a fork of VSCode (or whatever) will make me never use it. I wonder if they bet…
I think calling Open AI Codex or Claude Code "CLI" is a bit a of minomer. It's more of a GUI, just rendered in a terminal. I honestly think a "regular" for GUI for OpenAI Codex / Claude Code could be much better.