2011/4/20 Eliot Miranda <eliot.miranda@gmail.com>:
On Wed, Apr 20, 2011 at 9:51 AM, Camillo Bruni <camillo.bruni@inria.fr> wrote:
Objection! ;)
Using git has nothing to do with a file based system. The approach would be to use git as a storage backend for monticello. Git just stores 3 types of objects: commit, tree, blob. There are no files involved!! So this would be perfectly compatible with and image based system such as smalltalk.
see: http://book.git-scm.com/1_the_git_object_model.html
personal rant from here on >>>
However I see that smalltalkers tend to ignore the fact that there are other tools not written in smalltalk which are widely used and they actually work! For instance monticello. Although the model works perfectly fine, the UI is just plain crap, it does not provide a nice workflow nor is it readable... Git on the other hand might be too complex, but it lets do more stuff on the command line, in an easier fashion than the mc tool.
Smalltalkers tend to reinvent the wheel, which is sometimes nice, if its well designed and actually works, but many times its rather a waste of time, than just relying on existing working infrastructure that people outside smalltalk build.
What I see in Pharo is a good move towards making these tools work again, most of them are just old and ignore common UI principles.
And Smalltalk is not the holy grail, its just yet another programming language, which has nice syntax ;).
You're joking right? Â Smalltalk is not a programming language, it is an object system, including a programming language, a library, tools etc. Â Please, let's not completely misunderstand what Smalltalk is in this community.
I full agree, as like to say a well know Smalltalker here, Smalltalk is an objects environment who has a language (between other things).