Live data from Hacker News

Mercurial 4.0 Sprint Notes

groups.google.com

1–10 of 128 posts

Re: Mercurial 4.0 Sprint Notes

#2
Relevant quote:

  > Facebook is writing a Mercurial server in Rust. It will be distributed and
  > will support pluggable key-value stores for storage (meaning that we could
  > move hg.mozilla.org to be backed by Amazon S3 or some such). The primary
  > author also has aspirations for supporting the Git wire protocol on the
  > server and enabling sub-directories to be git cloned independently of a
  > large repo. This means you could use Mercurial to back your monorepo while
  > still providing the illusion of multiple "sub-repos" to Mercurial or Git
  > clients. The author is also interested in things like GraphQL to query repo
  > data. Facebook engineers are crazy... in a good way.

Re: Mercurial 4.0 Sprint Notes

#3

Relevant quote: > Facebook is writing a Mercurial server in Rust. It will be distributed and > will support pluggable key-value stores for storage (meaning that we could > move hg.mozilla.org to be backed by Amazon S3 or some such). The primary > author also has aspirations for supporting the Git wire protocol on the > server and enabling sub-directories to be git cloned independently of a > large repo. This means yo…

CTO of RhodeCode here. This is exciting, we need to take a look from our side how this would affect our product.

I really like that Mercurial is gaining some traction with the big guys, which tries to solve some nice problems at scale.

Re: Mercurial 4.0 Sprint Notes

#4

Relevant quote: > Facebook is writing a Mercurial server in Rust. It will be distributed and > will support pluggable key-value stores for storage (meaning that we could > move hg.mozilla.org to be backed by Amazon S3 or some such). The primary > author also has aspirations for supporting the Git wire protocol on the > server and enabling sub-directories to be git cloned independently of a > large repo. This means yo…

CTO of RhodeCode here. This is exciting, we need to take a look from our side how this would affect our product. I really like that Mercurial is gaining some traction with the big guys, which tries to solve some nice problems at scale.

Over here: https://www.mercurial-scm.org/wiki/4.0sprint

  >  - Goal is to open source the server, once it's more than just slideware.
So you might not be able to look at it just yet, but hopefully soon?

Re: Mercurial 4.0 Sprint Notes

#5

Earlier quoted context omitted.

CTO of RhodeCode here. This is exciting, we need to take a look from our side how this would affect our product. I really like that Mercurial is gaining some traction with the big guys, which tries to solve some nice problems at scale.

Over here: https://www.mercurial-scm.org/wiki/4.0sprint > - Goal is to open source the server, once it's more than just slideware. So you might not be able to look at it just yet, but hopefully soon?

Hopefully !

We spend a lot of time on our own to scale our Mercurial backend. Currently with the http based vcs-server and gevent we can support a lot of concurrent hg operations, but imho that thing can put it on the next level...

I wonder if it will support all things like phases etc ootb.

Re: Mercurial 4.0 Sprint Notes

#8
post #6

I had no idea Google and FB were dabbling with Mercurial. I checked it out years ago, but pretty much settled on Git. What are the advantages?

The biggest technical difference is the mostly immutable history, which is a feature or a drawback depending on who you talk to.

More subjectively, most people I've chatted to about it seem to find Mercurial's interface much easier to grok / pick up as a new user than Git's (which is somewhat notorious for its quirks).

There are other differences, but these stand out to me. That said, I use Git because adoption + community (and my experience with hg-git has been less successful than some... though it's been a while since I gave it a spin)

Re: Mercurial 4.0 Sprint Notes

#9
post #6

I had no idea Google and FB were dabbling with Mercurial. I checked it out years ago, but pretty much settled on Git. What are the advantages?

If you have a ton of files inside of one gigantic repo, the work facebook is doing on mercurial might help you out.

If you live in a saner world though, you'll probably benefit more from git's superior cli & tooling

Re: Mercurial 4.0 Sprint Notes

#10
post #7
post #6

I had no idea Google and FB were dabbling with Mercurial. I checked it out years ago, but pretty much settled on Git. What are the advantages?

They wrote about it here: https://code.facebook.com/posts/218678814984400/scaling-merc...

The big advantage to call out is that they found Mercurial much easier to add extensions to and more receptive to their issues with large monorepos. (For an idea of the scale, Facebook's repository I have heard is ~10× the size of mozilla-central, which is probably the largest public Mercurial repository.)
Post reply on HN