>>18
some special protocol
What's the big fucking deal with the git protocol? Don't most versions control systems have their own protocols? The git protocol exists because the way git repos are stored isn't well suited to HTTP, because it stores delta-compressed, whole files into packs, and those packs can't be split by HTTP if the client only needs a few objects from it; whereas Mercurial, I believe, stores reverse deltas, probably in separate files, which is much better for HTTP. But now there's a "Smart HTTP" CGI script to work around the HTTP issues.
Now all they need is Windows support that's at least half as good as hg
msysgit works great, I use it often. Works exactly like the Linux version does, so I'd say that its support is near 100% by now.
the scripting flexibility of hg
Scripting can be done with low-level plumbing in shell scripts, or with any one of the numerous git libraries.
cleaning up the gigantic mess of CLI options.
I'm not sure what you're referring to, but the man pages are pretty clear right now. If you're just complaining that there's
too many options, then I'd have to disagree; what's wrong with having features? If you don't want them, don't use them, but let others who need them have them!