3 ms·
I sometimes wonder what would have happened if Atlassian had stuck with Mercurial support on Bitbucket - I don't think they can pretend that switching to git di
by zabzonk 5mo ago
I sometimes wonder what would have happened if Atlassian had stuck with Mercurial support on Bitbucket - I don't think they can pretend that switching to git did very much for them. I love(d) Mercurial, and particularly TortoiseHg integration on Windows.
- eesmith 5mo agoIf they had, I wouldn't have switched to Sourcehut, at least not for a while. Though at some point I would have realized that Atlassian was the wrong fit for my needs as a single-dev, no-AI project and switched.
- faangguyindia 5mo agoFossil supports wiki, forum, issues but thing is, aren't coding agents tunned for git based workflows? many agents use git trees right? so it's unlikely that any git alternative will pickup from here?
- monsieurbanana 5mo agoI worry llm will increase inertia and make more difficult to adopt new technologies. But who knows? Maybe it would lower the barrier instead. If switching to fossil is just one agent.md instruction away and it brings useful features with minimal effort, it might be an easier sell than without them. After all, the new generation of programmers won't bother learning git anyway.
- vintagedave 5mo agoI had a video call with one of their staff when they announced removing it. I had a key (to me) Mercurial repo and was not keen to lose it. They said (I recall) that Mercurial was driven by a single person and when they left there was no one willing to fight for it. I still miss it too. We need a better git. For a while I thought it might be jj but it turns out it’s just as full of arcane commands as git is.