Hacker News Reader

Please make version control systems pluggable if you make a larger scope product. For a source nav product building it “on” git is fine. But once it has builds, issues etc it would be great if it also supported other version control systems. This is the biggest flaw of some of the existing players (e.g github).

I have high hopes that git will be replaced by something better, but the more products there are built on top of it, the harder it gets.

View on HN

Pluggability is very hard. Different version control systems have entirely different concepts of revisions.

It's very obvious, and much worse, when an IDE has plugins for VCS, as often the VC concepts aren't mapped well. When original git integration came out it was often terrible, because it forced git to behave like SVN.

I'm not saying we should tie ourselves into a single VCS, but tight integration has lots of benefits, and pluggabilty while maintaining those benefits is harsh bordering on impossible.

You might want to look at RhodeCode then, it supports now git,mercurial and subversion via it's vcsserver. Adding more in the future shouldn't be a problem because of all the abstraction in place.

Reply on news.ycombinator.com