They haven't built their own editor, they haven't built their own models; what have they actually built?
Well, they delivered something that is usable and useful for me and my team, and a lot of people I know, and I guess that’s what counts in business?
Cursor: Past, Present, and Future
31–40 of 61 posts
Re: Cursor: Past, Present, and Future
#32Re: Cursor: Past, Present, and Future
#33Earlier quoted context omitted.
I mean, they have built their own model: https://cursor.com/blog/composer And presumably they'll use the funding to build more than just a modified VSCode.
most likely a finetune of existing model
Composer-1 is very good for routine code edits.
Claude and Gemini get pulled in for hard problems and architecture.
Re: Cursor: Past, Present, and Future
#34> We’ve grown to a team of over 300 engineers, researchers, designers, and operators That last word, operators, I have seen used multiple times over the past couple of weeks to refer to managers and politicians. Is that the usage here too? If so, is this a new trend in the tech world? I’ve certainly heard of “political operators” in TV shows about Washington DC, but the usage in tech is new to me.
Re: Cursor: Past, Present, and Future
#35Earlier quoted context omitted.
Well, they delivered something that is usable and useful for me and my team, and a lot of people I know, and I guess that’s what counts in business?
I barely use the autocomplete features of Cursor, and for agentic coding, Claude Code blows Cursor Agent out of the water. I don't think Cursor has anything that cannot be replicated in a week or two other than the first mover advantage; certainly not an advantage that cannot be justified at 30B+ valuation.
cannot -> can
(the extra negative negated your point)
Re: Cursor: Past, Present, and Future
#36I am grateful to Cursor for ushering in the new age of coding beyond the "old" Github Copilot. I am also grateful to their VCs for subsidizing my coding. I am going to use their money to write subsidized code as long as the party lasts.
Re: Cursor: Past, Present, and Future
#37Ha. Does anyone run a total on how much VC funding has gone towards this goal? In aggregate?
Re: Cursor: Past, Present, and Future
#38They haven't built their own editor, they haven't built their own models; what have they actually built?
Well, they delivered something that is usable and useful for me and my team, and a lot of people I know, and I guess that’s what counts in business?
Re: Cursor: Past, Present, and Future
#39Earlier quoted context omitted.
What does Amp do better than Claude Code or Codex? I find the concept pretty appealing but the pricing is a bit scary.
It has better search and context management under the hood, which matters for big companies. But you can also see quantitatively that Sourcegraph produces the most accepted code: https://www.theinformation.com/articles/openai-catching-anth...
Re: Cursor: Past, Present, and Future
#40I love Cursor. I’m greedy to ask but is there a better alternative? Hard for me to imagine. I tried Copilot was no where near as good.
Now Claude code and Cursor are the best options imo, and I would say Cursor takes the edge for ide integration. Claude, as a separate thing to the ide, does mean you can do now flexible things like run it in a script loop.
Copilot doesn't get a shout in. It's fine for autocomplete but as a full agent it doesn't seem there yet.
If you're paying for it yourself Cursor seems to give the most bang for buck as well.