On Jun 26, 2014, at 3:52 PM, Esteban Lorenzano <[email protected]> wrote:
> On 26 Jun 2014, at 14:56, Sven Van Caekenberghe <[email protected]> wrote: > >> >> On 26 Jun 2014, at 19:07, Dale Henrichs <[email protected]> >> wrote: >> >>> I think that it is possible to most if not all of the git work support into >>> the Smalltalk development environment ... I am doing that for GemStone with >>> tODE[6] and I do find myself going to the go to the command line much less >>> frequently ... but in tODE I have built a git merge tool and a git diff >>> tool ... you can get the git history of a method from the browser, etc. >>> >>> Without a relatively high degree of tool integration it can be clunky to >>> use git ... I am very willing to share what I've done/learned in tODE with >>> Pharo tool builders and of course I think Thierry Goubier has actually been >>> ahead of me in several different areas ... >> >> That is my analysis: it works today, 'perfectly', but there is not enough >> tools support to make it as easy as Monticello as a whole is today. >> >> If these tools exist, or we can build them quickly based Dale's code, that >> would be cool (I guess its all OSProcess underneath, which I find so/so, a >> direct integration is better) that would be good. >> >> Would having this change our world fundamentally ? No, IMHO >> Is it worth the effort, is the ROI there ? I don't think so > > I disagree here. I think moving our development to git will change deeply > (for good) our community processes and then I think it totally worths the > effort. big +1 here The social benefit of having your code exposed in places like github outweighs by at an astronomical scale the current lack of amazing mergetools If your code cannot be exposed without friction you’re done The noise of the jungle of 3-new-libraries-per-day-that-can-be-installed-in-one-shot will make your work invisible
