- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo+Git cons?

by Max Leske

> On 04.12.2014, at 09:47, kilon alios <kilon.alios(a)gmail.com> wrote: > > > > What are the benefits that justify the effort to reimplementing git in smalltalk ? > Iâm not sure we need to discuss that, since there already is FileSystem-Git which *is* an implementation of Git in Smalltalkt...

Dec. 4, 2014

Re: [Pharo-dev] Pharo+Git cons?

by kilon alios

What are the benefits that justify the effort to reimplementing git in smalltalk ?

Dec. 4, 2014

Re: [Pharo-dev] GTPlayground cache

by Tudor Girba

Why not? Was there a change in the Pharo image? (I do not have access to the code right now) Doru On Thu, Dec 4, 2014 at 8:57 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > Since 40393 the play-cache is not read when you open the first > GTPlayground in a fresh image. > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 4, 2014

Re: [Pharo-dev] Pharo+Git cons?

by Esteban Lorenzano

> On 04 Dec 2014, at 09:24, Norbert Hartl <norbert(a)hartl.name> wrote: > >> We need a better-than-git Smalltalk thing :) yeah, we need a lot of things. But who will put the bell on the cat's neck? just dreaming of what we *could* have will make us never have anythingâ¦ is not that horizons are bad, they are needed to show the path to follow. But not to accept the small improvements in the name of some super-goal we are never close (because, of course, horizons move constantly) is prone to immobility. Esteban

Dec. 4, 2014

Re: [Pharo-dev] Pharo+Git cons?

by Max Leske

> On 04.12.2014, at 09:07, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2014-12-04 8:27 GMT+01:00 Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: > >> On 04.12.2014, at 07:24, Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> >> Le 03/12/2014 14:02, Ben Coman a Ã©crit : >>> Eliot Miranda wrote: >>>> >>>> [and apologies for being deliberately incendiary but I *hate* the >>>> movement away from tools in Squeak/Pharo. It is a movement towards >>>> stasis and death, and personally I'm enjoying life too much]. >>> >>> So what we need is a native Smalltalk git ;) >> >> We need a better-than-git Smalltalk thing :) >> >>> Yes I know... more work with limited resources, but native git its being >>> done in other places... (not sure how successfully) >> >> I can give you a head start. There is some Smalltalk code to reuse; it's called FileSystem-Git, or FS-Git. >> >> https://github.com/dalehenrich/FSGit <https://github.com/dalehenrich/FSGit> >> >> https://github.com/theseion/fs-git <https://github.com/theseion/fs-git> >> >> http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git <http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git> >> http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem <http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem> >> >> They do lack a bit of activity. > > Thatâs because they should be superseded by the libgit2 bindings. > > If I'm not mistaken, they originally were what Ben suggested: a complete git reimplementation in Smalltalk via a FileSystem abstraction layer. The idea is great and works quite well. There are two problems however and they are the reasons I chose to go with bindings: - such an implementation is very hard to maintain and the chance of introducing bugs is just off the charts - performance and memory allocation need a lot of working around (and praying) > The Pharo "whole" export to github would be based on that work, along with that 'almost like FileTree, but not the same' file format. Not quite. The export simply produces (FileTree) artifacts and writes them to disk. There is no hard dependency to FileSystem-Git (although that might have been the plan at some point). > > But correct me if I got that wrong. > > > This is the right repo: http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git <http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git> (the github version is outdated). > > Thanks for the reminder (and the hard work you're putting into the libgit2 bindings), Thank you for your patience :) > > Thierry > > >> >> Thierry >> >>> >>> Javascript >>> https://github.com/creationix/js-git <https://github.com/creationix/js-git> >>> >>> Java >>> http://eclipse.org/jgit/ <http://eclipse.org/jgit/> >>> >>> Haskall >>> http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/ <http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/> >>> https://github.com/vincenthz/hit <https://github.com/vincenthz/hit> >>> >>> Python >>> https://www.samba.org/~jelmer/dulwich/ <https://www.samba.org/~jelmer/dulwich/> >>> >>> Perl >>> https://metacpan.org/pod/Git::PurePerl <https://metacpan.org/pod/Git::PurePerl>

Dec. 4, 2014

Re: [Pharo-dev] Pharo+Git cons?

by Norbert Hartl

> Am 04.12.2014 um 07:24 schrieb Thierry Goubier <thierry.goubier(a)gmail.com>: > > Le 03/12/2014 14:02, Ben Coman a Ã©crit : >> Eliot Miranda wrote: >>> >>> [and apologies for being deliberately incendiary but I *hate* the >>> movement away from tools in Squeak/Pharo. It is a movement towards >>> stasis and death, and personally I'm enjoying life too much]. >> >> So what we need is a native Smalltalk git ;) > > We need a better-than-git Smalltalk thing :) > +1 darcs anyone? Norbert >> Yes I know... more work with limited resources, but native git its being >> done in other places... (not sure how successfully) > > I can give you a head start. There is some Smalltalk code to reuse; it's called FileSystem-Git, or FS-Git. > > https://github.com/dalehenrich/FSGit > > https://github.com/theseion/fs-git > > http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git > http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem > > They do lack a bit of activity. > > Thierry > >> >> Javascript >> https://github.com/creationix/js-git >> >> Java >> http://eclipse.org/jgit/ >> >> Haskall >> http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/ >> https://github.com/vincenthz/hit >> >> Python >> https://www.samba.org/~jelmer/dulwich/ >> >> Perl >> https://metacpan.org/pod/Git::PurePerl > >

Dec. 4, 2014

Re: [Pharo-dev] Pharo+Git cons?

by Esteban Lorenzano

> On 04 Dec 2014, at 09:07, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2014-12-04 8:27 GMT+01:00 Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: > >> On 04.12.2014, at 07:24, Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> >> Le 03/12/2014 14:02, Ben Coman a Ã©crit : >>> Eliot Miranda wrote: >>>> >>>> [and apologies for being deliberately incendiary but I *hate* the >>>> movement away from tools in Squeak/Pharo. It is a movement towards >>>> stasis and death, and personally I'm enjoying life too much]. >>> >>> So what we need is a native Smalltalk git ;) >> >> We need a better-than-git Smalltalk thing :) >> >>> Yes I know... more work with limited resources, but native git its being >>> done in other places... (not sure how successfully) >> >> I can give you a head start. There is some Smalltalk code to reuse; it's called FileSystem-Git, or FS-Git. >> >> https://github.com/dalehenrich/FSGit <https://github.com/dalehenrich/FSGit> >> >> https://github.com/theseion/fs-git <https://github.com/theseion/fs-git> >> >> http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git <http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git> >> http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem <http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem> >> >> They do lack a bit of activity. > > Thatâs because they should be superseded by the libgit2 bindings. > > If I'm not mistaken, they originally were what Ben suggested: a complete git reimplementation in Smalltalk via a FileSystem abstraction layer. The Pharo "whole" export to github would be based on that work, along with that 'almost like FileTree, but not the same' file format. > > But correct me if I got that wrong. it was Camilloâs work/idea, not Benâs. and well, it was a great idea, but never more than an experiment. I wanted it too, but I didnât continue the work because it would be different from monticello and community has proved been refractory to ideas that goes further it. so I get back to the other idea (Yours, Max) which was made monticello work with git. It will not be complete, but it will be a start. not that I have had actually time to work on it, but I will continue Max work as soon as I can allocate some time. Esteban > > > This is the right repo: http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git <http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git> (the github version is outdated). > > Thanks for the reminder (and the hard work you're putting into the libgit2 bindings), > > Thierry > > >> >> Thierry >> >>> >>> Javascript >>> https://github.com/creationix/js-git <https://github.com/creationix/js-git> >>> >>> Java >>> http://eclipse.org/jgit/ <http://eclipse.org/jgit/> >>> >>> Haskall >>> http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/ <http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/> >>> https://github.com/vincenthz/hit <https://github.com/vincenthz/hit> >>> >>> Python >>> https://www.samba.org/~jelmer/dulwich/ <https://www.samba.org/~jelmer/dulwich/> >>> >>> Perl >>> https://metacpan.org/pod/Git::PurePerl <https://metacpan.org/pod/Git::PurePerl>

Dec. 4, 2014

Re: [Pharo-dev] Pharo+Git cons?

by Thierry Goubier

2014-12-04 8:27 GMT+01:00 Max Leske <maxleske(a)gmail.com>: > > On 04.12.2014, at 07:24, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > Le 03/12/2014 14:02, Ben Coman a Ã©crit : > > Eliot Miranda wrote: > > > [and apologies for being deliberately incendiary but I *hate* the > movement away from tools in Squeak/Pharo. It is a movement towards > stasis and death, and personally I'm enjoying life too much]. > > > So what we need is a native Smalltalk git ;) > > > We need a better-than-git Smalltalk thing :) > > Yes I know... more work with limited resources, but native git its being > done in other places... (not sure how successfully) > > > I can give you a head start. There is some Smalltalk code to reuse; it's > called FileSystem-Git, or FS-Git. > > https://github.com/dalehenrich/FSGit > > https://github.com/theseion/fs-git > > http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git > http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem > > They do lack a bit of activity. > > > That's because they should be superseded by the libgit2 bindings. > If I'm not mistaken, they originally were what Ben suggested: a complete git reimplementation in Smalltalk via a FileSystem abstraction layer. The Pharo "whole" export to github would be based on that work, along with that 'almost like FileTree, but not the same' file format. But correct me if I got that wrong. > This is the right repo: > http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git (the github > version is outdated). > Thanks for the reminder (and the hard work you're putting into the libgit2 bindings), Thierry > > > Thierry > > > Javascript > https://github.com/creationix/js-git > > Java > http://eclipse.org/jgit/ > > Haskall > http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/ > https://github.com/vincenthz/hit > > Python > https://www.samba.org/~jelmer/dulwich/ > > Perl > https://metacpan.org/pod/Git::PurePerl > > > > > > > >

Dec. 4, 2014

GTPlayground cache

by Nicolai Hess

Since 40393 the play-cache is not read when you open the first GTPlayground in a fresh image.

Dec. 4, 2014

Re: [Pharo-dev] Pharo+Git cons?

by Max Leske

> On 04.12.2014, at 07:24, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 03/12/2014 14:02, Ben Coman a Ã©crit : >> Eliot Miranda wrote: >>> >>> [and apologies for being deliberately incendiary but I *hate* the >>> movement away from tools in Squeak/Pharo. It is a movement towards >>> stasis and death, and personally I'm enjoying life too much]. >> >> So what we need is a native Smalltalk git ;) > > We need a better-than-git Smalltalk thing :) > >> Yes I know... more work with limited resources, but native git its being >> done in other places... (not sure how successfully) > > I can give you a head start. There is some Smalltalk code to reuse; it's called FileSystem-Git, or FS-Git. > > https://github.com/dalehenrich/FSGit > > https://github.com/theseion/fs-git > > http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git > http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem > > They do lack a bit of activity. Thatâs because they should be superseded by the libgit2 bindings. This is the right repo: http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git <http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git> (the github version is outdated). > > Thierry > >> >> Javascript >> https://github.com/creationix/js-git >> >> Java >> http://eclipse.org/jgit/ >> >> Haskall >> http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/ >> https://github.com/vincenthz/hit >> >> Python >> https://www.samba.org/~jelmer/dulwich/ >> >> Perl >> https://metacpan.org/pod/Git::PurePerl >> >> >> >> > >

Dec. 4, 2014