[Cuis] How Open Source Software Blooms: Gource Version Control Visualizations From Google

[Germán Arduino]

Hi:

2013/1/7 H. Hirzel <hannes.hirzel at gmail.com>

> Hello,
>
> Yes, thank you as well for this contribution, Angel.
>
> Amazing to watch these visualizations.
>
> From the perspective of the examples given (PhP, Python, OpenOffice,
> ....) the forking of Squeak to Pharo and Cuis (and other earlier forks
> like Scratch and Etoys) seems not to be  something extraordinary. It
> is the way how open source software is developed to suit people's
> need.
>
> Interesting to see how pieces of code are exchanged forth and back
> between the different forks. This is actually happens as well between
> Squeak (www.squeak.org) , Pharo (http://www.pharo-project.org/)  and
> Cuis. All share a common virtual machine and _very_ important, the
> same license (MIT). This makes things go smooth.
>
> It is helpful to check out how something is done in Squeak and Pharo
> in comparison to Cuis for example. It allows to search for good
> solutions. Having different forks unblocks the development process in
> many ways as it allows to be exploratory.
>
> For Cuis one of the distinctive features is that we really want to
> make good use of github.
> (as of now we have just started to do that, thank you Angel for your
> guidance   :-)
>
>
A little comment here, I think the greatest value of Cuis is cleaning and
simplicity,
is really understandable. I can not say the same about Squeak nor Pharo.

I'm going deep in both images (Squeak 4.4 and Pharo 1.4) to make the
cleanest possible
implementation of network features needed in Cuis and the nightmare is
important (Said
with all respect, of course).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jvuletich.org/pipermail/cuis_jvuletich.org/attachments/20130107/0cdc27e5/attachment-0002.html>