61–70 of 519 posts
Cursor is allegedly worth $60B. That is a higher market cap than Mercedes Benz group, which is profitable and has $144B revenue . But the website uses 100% CPU. And this is a beta for paid plans, not a GitHub alternative.
Jokes aside, this is a smart move by Cursor. As you can probably tell by the comments here, it's not for the experienced developers, but it will be a natural choice for vibe coders.
You get:
- Self hosting your git hosting (if you want)
- Self hosting your issues/PRs (if you want)
- Self hosting your CI (if you want)
- Github-like social features (I have one account, I can follow, star, add issues and PRs to any repo on tangled)
My guess is there will be at least dozens if not hundreds.
Earlier quoted context omitted.
What I don't understand from the blog post is what's different in this offering than github - is it just the agentic tie ins where I can ask my agent to make changes while browsing the PR? Are there any fundamental differences, ie ways of working that solve the worktrees problem?
Expect a lot more from us. We wanted to release a beta so people could start experimenting with our scalability and extensibility themselves. Over the next few weeks, you can expect a handful of features starting to change source control to better understand and work with agents.
I have a lot of dev tooling which assumes code is stored on public GitHub and/or GitHubEnterprise. This produces some degree of lock-in, in that all that code would have to be rewritten to migrate to something else. (Yes, AIs can help, but they still don't make migration effortless.)
The major Git hosters tend to implement roughly the same concepts, albeit with lots of little variations. It would be great if there were some sort of standardised API everyone implemented. In the absence of that, it makes sense for people to emulate the incumbent's APIs as a de facto standard, just like how other vendors copy OpenAI's APIs for talking to LLMs.
Hi all, my name is Tomas. I am one of the developers on Origin, and I was one of the founders of Graphite ( https://graphite.com ). Happy to answer any questions about Origin or source control in general!
What a timing! I wonder if they were waiting for a major githut incident :D
Earlier quoted context omitted.
What I don't understand from the blog post is what's different in this offering than github - is it just the agentic tie ins where I can ask my agent to make changes while browsing the PR? Are there any fundamental differences, ie ways of working that solve the worktrees problem?
The idea is that it's like Github but it stays up even as your commit/CI frequency increases. As a customer I'm stoked and looking forward to fully switching over as that's exactly what I want.
It's funny that they are trying to replace GitHub by the part that already has multiple alternatives tho. This will fail without a doubt.