2014-11-28 14:40 GMT+01:00 Ben Coman <btc@openinworld.com>:

kilon alios wrote:

I forgot to add that git comes with excellent gui clients that are far more powerful and elegant that what Pharo offers currently .

We started late.� We had tools reasonably suited for our needs which we were comfortable with.� I think/hope that once libgit is "released" in Pharo and the wider community becomes more familiar with it, it stimulates us to develop tools to rival the others.� Tools that non-Smalltalkers also find useful, and when they want to add a feature, they are motivated to learn Pharo.� I think this is a small additional benefit of tighter integration of git in Pharo.

But underlying this is the hypothesis that you will be able to master the complexity of git from within Pharo, which is ambitious.

Given how complex git is and the use cases around it, I personaly do not underestimate that task. I do know that, probably, if git gets totally integrated within Pharo, it will not fit my professional use case and I will have to resort to something else[*]. In the same way that people who knows and use git (and github) everyday do prefer to stay with FileTree and command line git (and external tools) than switch to GitFileTree (which is a plain automation layer above FileTree and git).

We are now at four attempts[**] at writing git support for Pharo in no less than three or four years, with two dead,� one working for two platforms out of three and one under development for already a while. This shows that we need a bit of humility in promising the perfect git integration and tools.

Thierry

[*] But it will fit the Pharo team use case perfectly well ;)

[**] I'm finding new ones on github while searching:
https://github.com/JumpIntoSqueak/metacello-git
https://github.com/timfel/gitocello
https://github.com/theseion/fs-git
https://github.com/theseion/LibGit
https://github.com/theseion/LibGit2-bindings

�

cheers -ben