On 2013-03-20, at 10:50, Davorin Rusevljan <[email protected]> wrote:
> On Wed, Mar 20, 2013 at 2:58 AM, Victor Stan <[email protected]> wrote: > >> Why are SmallTalk projects/source code hosted on SS3 Gemstone instead of >> Git/GitHub? >> >> I'm coming to SmallTalk from the world of web development with open source >> software, primarily Rails, and I'm very familiar with the amazing social >> network/source code repository that is GitHub. It is truly an industry >> defining entity, so many open source projects have been able to harness the >> ease of use, features and community around Git and GitHub. >> >> At the moment, as I'm trying to learn more about SmallTalk and Pharo >> especially, (my primary interest in Pharo is to use it as a web development >> platform), I am a bit shocked, if I may be frank, at the tooling used for >> source code and open source project management. I see that the popular >> trend now is to move to SS3/Gemstone, and I appreciate anyone that helps >> open source development/projects, but I can't see how they can even come >> close to the functionality of GitHub for source code hosting and OS project >> management, so I pose the question: is there an effort, why or why not, to >> start integrating with GitHub and Git for source code management? >> >> I know that historical precent and the tools built into Pharo/SmallTalk >> images, like Monticello are predecessors to GUI source control, but given >> the leaps that Git has managed to take, in distributed source code >> management, how does the existing SmallTalk community feel about it's >> current tooling in this regard? >> >> > > First welcome! > > As others have said, there are efforts to use git as source control and I > am looking forward to their progress. As for slow adoption of git, I think > the following might be some of the reasons: > > 1) file based VCS, are a bit rude for Smalltalk, which operates on smaller > source granularity, and typicall Smalltalk based VCS handle that in more > natural way not true... and just for the record, Monticello is file-based too, it does not store any high-level information. If you store each method as separate file as done with filetree you get exactly the same granularity as monticello. see: https://github.com/pharo-project/pharo-core > 2) Monticello is distributed VCS, and I am not so sure that it compared to > git lacks many features that would be esseintial to Smalltalk developer. > (but since I am only causal user of both, I might be wrong on this) as a model monticello and git overlap pretty well, however many things are much more implicit in monticello than in git (namely branches).
