Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Taking a decentralized application like Git back to centralization is a step in the wrong direction, it's exactly why Git was created.


Decentralization is a cool concept, but didn't GitHub and BitBucket emerge because a centralized server was in demand? Git is a good tool for many uses, but when was the last time you pushed directly to a peer's repo on their machine? How many firewall and reverse proxy configurations did you have to setup to be able to do it?


It's kinda the standard procedure of securing your machine's ssh, I'd recommend trying to setup a bare repo and put it online so you see how easy it is to make it work, that's not Github but it's more than enough for your org, in fact before Github was created that's how we did it, it doesn't really take more than 1 afternoon to set it up, multi-user and all the other jazz.

But Github and Bitbucket aren't examples to compare Diversion to though, Github is just a node in the decentralized network of Git repos (your users, or whoever cloned). They even use an example of this feature, how they were able to recover after a mess-up, then with SVN that couldn't be done and they'd have really lose more than a month of work.

There's one of the reasons why Git was created, to make it easier to resolve conflicts, if you just want a main / children branches structure in one server then use SVN / Diversion but then don't complain when you have a branch "locked" and you cannot get your job done.

Diversion makes 100% sense if you follow the silly "one repo for the whole org" way big companies do, which still doesn't make any sense to me.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: