I really like Cursor, however I think ultimately a good open-source alternative will likely overtake it soon.
Keep in mind Cursor is just a fork of VSCode, with AI features that are pretty much just embedded extensions. Their product is great, but many users would prefer a bring-your-own-key & selecting their own model providers.
On the contrary. Most enterprise users will prefer one package they can buy and not buy the thing piece wise.
Big reason why VSCode won was because they were able to provide a lot of things out the box saving the user round trip through the config hell rabbit hole modern vim/emacs ecosystems are.
If you want to sell developer tooling products, provide as much as possible out of the box.
People want to solve their problems using your tool. Not fix/build problems/missing features in your tool.
A big reason copilot spread so fast is because people already trust GitHub with their code - enabling AI doesn't really modify risk. If GH wanted to break TOS and train on your code they could, even without copilot, if you're using GH for private repos.
Any other third party needs to get vetted/trusted - I would be the first to doubt an AI startup.
As more and more people use co-pilot or even cursor, there is likely to be a mad increase in productivity.
But also note, there is likely to be a situation like the early days of internet where people write lots of code, but also bug ridden and unreadable code.
It will take a few years for things to return to routine.
Meh - personally I see copilot as a mild boost/auto complete++ - helps me type out stuff that's obvious in context but needs to be typed out anyway.
I've had it disabled when switching between environments and sometimes not notice for a day - depending on what I'm doing.
That used to be a valid problem, but times have changed. For instance, Neovim has things now like kickstart.nvim and lazy.nvim that solve this problem. I've been test-driving LazyVim for the past month or so and I don't have to config anything anymore because the updates and plugins are sane choices.
vi(m) is still the best command line editing tool out there. And I used is almost a dozen times everyday.
But the IDE ship sailed long back. Its just that the modern IDE's simply do a lot out of the box that is just not possible to configure quickly, or well enough outside using packages. Most of the times the packages don't work well with each other.
Like the Python's formatter often interferes with vim's modal editing etc.
With AI, this will take it a level further apart.
With that argument, it would be reasonable to assume Microsoft will just clone the key features (Composer etc) and bake them into the next generation of Copilot on VSCode.
Microsoft has its top-tier distribution advantages, plus they can build native integrations with Github/Azure etc to take things to a new level - think one-click deployments built into VSCode.
In fact, given the rising popularity of Replit/Vercel/etc I wouldn't be surprised if Microsoft is cooking as we speak.
That relies on MS' ability to deliver something both complete, comprehensive + have a good UX.
Most of the time they can deliver on...some fraction of some of those.
This is just the AI version of "oh they have Visual Studio + C# + Azure, C# can do FE + BE with ASP.net etc etc so why would anyone ever use anything else?"...and yet, here we are.
They'll deliver some janky, combo of features, it'll be stapled on top of VS Code, it'll be about 65% as good as everything else, but you've got to be all-in-on-MS to really get the value out of it, which will be great for a few enterprise clients, and middling to average for everyone else.
Open Source versions off this will be available soon enough, self-hosted models are only getting better, many orgs are loathe to spend anymore than the absolute minimum on dev-tools (why would they pay for fancy ML stuff that devs will want to run personal versions of anyways) sowhat's the real moat or value prop here?
I agree with your general point, but there is already a bring-your-own-key and select your own model providers option in Cursor.
The option you mentioned only works in the chat panel, not with other killer features that utilize the cursor.
Sadly they disable the Compose feature when using your own Claude key
They broke the openrouter integration though; it worked and now it does not anymore. Not sure if it was intentional or not, but it is a PITA.
continue(yc) is an open source vscode extension. The best thing about cursor is their auto complete feature, their own fine-tuned model. It will be a while for others to build something close to it.
How much better is cursor than continue? I've been trying continue with codestral and am only moderately impressed so far.
Not sure about continue, but I use Cursor for work, and it's really good at predicting simple operations. I rarely use it to actually generate code but it's pretty good at completing the code I'm already writing / the thing I'm already doing.
If you want to talk about in house autocomplete models, Supermaven has superior autocomplete, IMO.
What alternative open source solutions are currently competing with it?
I've been using https://github.com/VictorTaelin/AI-scripts together with my own nvim plugin that I should publish soon-ish.
Also there's https://github.com/yacineMTB/dingllm.nvim which seems promising but quite wip.
We really need a model that can integrate with the LSP though - so it never generates LSP invalid code.
That's what we are doing at Aide (shameless plug since I work on Aide)
I think using the LSP is not just a trivial task of grabbing definitions using the LSP, there is context management and the speed at which inference works. On top of it, we also have to grab similar snippets from the surrounding code (open files) so we generate code which belongs to your codebase.
Lots of interesting challenges but its a really fun space to work on.
https://aide.dev/
The Rstudio project Positron isnt quite the same - but its super dope: https://www.appsilon.com/post/introducing-positron
https://github.com/posit-dev/positron/blob/main/README.md
Sounds to me like Rabbit R1. A company picks up existing open source tools, builds their own extension/UI on top, and ship as something entirely new and novel. It'll grab a lot of attention short term, but others will quickly figure out how to make their own implementation that runs directly on the existing open source tools.