thoughts on veracity so far...

summary: Much depends on what exactly they mean by things like "conservative immutability"; details below. Overall, not impressed.

(1) Conservative immutability is for servers -- it may not be the default but all it takes in git is a one-time "git config --global receive.denyNonFastForwards true"). If you're going to force that on my desktop-side clone also, you're needlessly cramping my style. I make dozens of small commits as I test piece by piece and fix things, but when I finally push it's between 1 and 5 neatly ordered commits with proper commit messages.

(2) Any VCS that claims "Formal rename" as a plus point is not worth considering. While this might sound esoteric to many, trust me if you ever have to track down past changes to a piece of code that moved from one file to another at some point, you need it. See text surrounding the first picture in if you need a sample.

(3) File locks will appeal to people who want to version control non-text stuff like ODT/ODS/ODP or their legacy equivalents. That's one feature I'd like to have in git, but it seems to me is inherently at variance with the "D" in DVCS. If I go home for the weekend, start working on files, but I don't connect till Monday morning, and if someone locks a file on Saturday morning, how does that lock stop me from editing and committing locally on Sunday?

(4) Skein is not officially sha-3 yet, so this is just pandering to Bruce ;-) (ok this was mostly a joke; I'm a great fan of the guy also)

(5) User accounts instead of devolving to something external? Uh oh... smells like SVN all over again; I remember when 1.6 came out they boasted "we now have encrypted passwords" or some such nonsense. (I know I read that in a cover article in LFY -- an Indian Linux (print) magazine about a year or so ago, maybe a bit more)

(6) I'm not a fan of webby stuff so the "integrated web interface" will leave me cold but I'm sure most people will lap it up. I predict this will be the single biggest feature that will be touted when eventually this becomes credible enough to go head-to-head against git, just like "Windows support" was the big one for Mercurial.

(7) Not a big fan of JavaScript but nothing against it either. But more importantly, does this mean hooks etc., can only be written in JS? That would suck a wee bit in terms of flexibility. Git's hooks can be in any language you wish to use.

(8) bug tracking, burndown charts, build tracking: Not that pandering to PHBs is wrong per se, but I'm a firm believer in using multiple tools and integrating them externally -- harder to do initially but you get real experts within your company, compared to installing something that does it all.

Of course, in a world where not everyone believes that, someone who does the opposite will always find a place. Good for them I guess...


I'm only looking at fundamental design decisions, ignoring things like bisect not being available (which that doesn't sound like a permanent problem -- they just haven't gotten around to it yet; although it doesn't even say "coming soon").
Shared publiclyView activity