I'm starting to wonder whether operating a shared #code-hosting platform is only possible with sponsorship. #Gitorious collapsed because their paid hosting couldn't cover their costs (which includes the cost of free hosting). I don't believe #Github ever publicly released figures, but I do remember hearing a rumor that they were not profitable before #Microsoft purchased them. #Bitbucket still persists, but #Atlassian has made so many changes to their offerings that IMO, using their platform is putting everything that touches it at risk. #SourceForge went to all sorts of dangerous extremes to try to monetize the huge number of repositories they host (most of which appear to be residue of projects that have either died or moved their active repos elsewhere).
You'll notice that #Git is not in that list. I'm having to use git whenever I deal with other people's code projects, so I already know that it isn't tailored for my needs.
Correction: #Pijul ... it is a #dvcs / #scm system written in #Rust, and an evolution of some of the ideas behind #Haskell's #Darcs, including fleshing out the theoretical basis and solving a couple of major bugs.
@geniusmusing I find #git to be too big and complex for my needs (and arguably for most projects). I know it βwonβ and even some projects that formerly used another #VCS ( such as Mercurial #hg, #darcs, Bazaar #bzr / Breezy #brz ) are switching.
In the plans: a very limited #Kallithea install (with git and Mercurial) and #Fossil for Federati ... when I have more funds and energy to devote to getting it going on its own VPS.
@moonman My feelings exactly. I didn't have anything original there ( #Github ) in the first place, but I had patches for others' projects. I removed everything several years ago. Yes, a couple of potential employers have passed on hiring me because my GH account was empty. I just (A) don't want to support centralized facilities like GH or SourceForge any more, when you can host your own #git / #hg / #darcs / fossil; and (B) as my role at work has changed more toward user support, I'm not creating or using such patches any more, so if someone found and started using them, they'd be potentially doing it wrong / importing security holes.
( For a while, I had my own #Fossil repo with some original stuff, but thanks to hosting changes are $EMPLOYER work scheduling / hotel Internet, that's all gone, too. )
@bthall Iβm sure thereβs an API document for #Pijul somewhere. Or that may be an area where it is similar to something else, such as #Darcs. Anyway, if you find said document, you should be able to make a fully functioning client in #Python.
@xj9 @moonman #Fossil is my favorite. #Git is too complicated for anything I've ever done. (Planning to look at Mercurial #hg and #Darcs and Bazaar #bzr sometime.)
@tekk to continue with tradeoffs, you need to bear in mind when considering #darcs that their merge algorithm will occasionally bump into exponential (that is, 2^n) cases. Projects often dismiss it based on performance because of it.
If #git isn't the right version-control system for your work, there are others that may or may not fit your needs. Look at #hg (mercurial), #bzr (bazaar), #fossil, #darcs, or #svn (subversion). I know svn has a gui tool available for Windows. Not sure what kind of gui tools the others may offer.