Live data from Hacker News

I kind of killed Mercurial at Mozilla

glandium.org

31–40 of 250 posts

Re: I kind of killed Mercurial at Mozilla

#31

I've heard this point of view many times, but cannot find an extensive explanation of it. Could anyone elaborate on the issue with the GitHub review UI/UX? > I hate the GitHub review UI with a passion. At least, right now, GitHub PRs are not a viable option for Mozilla [...] the more general shortcomings in the review UI.

See https://news.ycombinator.com/item?id=37836932 by a Mozilla employee

Re: I kind of killed Mercurial at Mozilla

#33

Earlier quoted context omitted.

That change was so dumb. Mercurial support was the bit that put them as something different from github. Once they didn't have it anymore, why would anyone use them at all?

So since you are knowledgeable about the fact that this decision was "dumb", you must also know approximately what proportion of their users were dependent on hg for their workflow ? My priors would put it at less - likely far less - than 1%. But please share your knowledge.

Not true. I looked at the complete list of hosted projects on Bitbucket just when it was shut down and I recall that at least 10% of all repos ever created on Bitbucket were hg repos.

Re: I kind of killed Mercurial at Mozilla

#34

I've heard this point of view many times, but cannot find an extensive explanation of it. Could anyone elaborate on the issue with the GitHub review UI/UX? > I hate the GitHub review UI with a passion. At least, right now, GitHub PRs are not a viable option for Mozilla [...] the more general shortcomings in the review UI.

bitbucket is worse, reviewees can resolve reviewer's comments (github has this too turns out), after file changes, comments disappear

Re: I kind of killed Mercurial at Mozilla

#35

Earlier quoted context omitted.

That change was so dumb. Mercurial support was the bit that put them as something different from github. Once they didn't have it anymore, why would anyone use them at all?

One huge advantage for them compared to GitHub is that they offer an on-prem version. That is much more relevant than Hg support of all things. It also gets bundled with Jira and Confluence.

The hosted Bitbucket and Bitbucket Server (formerly called Stash) only share the name. They are completely different implementations and Bitbucket Server never supported Mercurial.

Re: I kind of killed Mercurial at Mozilla

#37

Earlier quoted context omitted.

That change was so dumb. Mercurial support was the bit that put them as something different from github. Once they didn't have it anymore, why would anyone use them at all?

So since you are knowledgeable about the fact that this decision was "dumb", you must also know approximately what proportion of their users were dependent on hg for their workflow ? My priors would put it at less - likely far less - than 1%. But please share your knowledge.

In the announcement they mentioned that less than 1% of new users were choosing hg. It was probably slightly higher for old users.

> In fact, Mercurial usage on Bitbucket is steadily declining, and the percentage of new Bitbucket users choosing Mercurial has fallen to less than 1%.

https://bitbucket.org/blog/sunsetting-mercurial-support-in-b...

Re: I kind of killed Mercurial at Mozilla

#39

I've heard this point of view many times, but cannot find an extensive explanation of it. Could anyone elaborate on the issue with the GitHub review UI/UX? > I hate the GitHub review UI with a passion. At least, right now, GitHub PRs are not a viable option for Mozilla [...] the more general shortcomings in the review UI.

One issue I was discussing with a colleague just the other day is that you cannot leave a comment on lines that are not "part of the diff" (changed or context), which is sometimes really useful for "see this thing over here".
Post reply on HN