Thanks by share.<br><br>About repositories I feel very comfortable working with GitHub and really I can't saw any sense to the development effort of SmalltalkHub only to? Being built in smalltalk? But paying the price of being isolated of all the rest of the developers that are currently using GitHub....<br>
<br>Just an opinion.<br><br>Cheers.<br><br><br><div class="gmail_quote">2012/12/25 Juan Vuletich <span dir="ltr"><<a href="mailto:juan@jvuletich.org" target="_blank">juan@jvuletich.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
FYI...<br>
<br>
-------- Original Message --------<br>
From: - Tue Dec 25 22:24:04 2012<br>
X-Mozilla-Status: 0001<br>
X-Mozilla-Status2: 00800000<br>
X-Mozilla-Keys: <br>
Message-ID: <<a href="mailto:50DA51B0.7000702@jvuletich.org" target="_blank">50DA51B0.7000702@jvuletich.<u></u>org</a>><br>
Date: Tue, 25 Dec 2012 22:24:00 -0300<br>
From: Juan Vuletich <<a href="mailto:juan@jvuletich.org" target="_blank">juan@jvuletich.org</a>><br>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)<br>
MIME-Version: 1.0<br>
To: Ron Teitelbaum <<a href="mailto:ron@usmedrec.com" target="_blank">ron@usmedrec.com</a>><br>
CC: 'The general-purpose Squeak developers list' <<a href="mailto:squeak-dev@lists.squeakfoundation.org" target="_blank">squeak-dev@lists.<u></u>squeakfoundation.org</a>>, 'dimitris chloupis' <<a href="mailto:thekilon@yahoo.co.uk" target="_blank">thekilon@yahoo.co.uk</a>>, <a href="mailto:stephane.ducasse@gmail.com" target="_blank">stephane.ducasse@gmail.com</a><div class="im">
<br>
Subject: Re: [squeak-dev] Squeaksource, Squeak and Pharo..<br></div>
References: <CAJbhyRFcERf5+2hxSU-Zj-<u></u>ikxGjt-e=<a href="mailto:NZs1XrKP5-apf7btcgQ@mail.gmail.com" target="_blank">NZs1XrKP5-apf7btcgQ@<u></u>mail.gmail.com</a>> <<a href="mailto:1356020957646-4660342.post@n4.nabble.com" target="_blank">1356020957646-4660342.post@<u></u>n4.nabble.com</a>> <<a href="mailto:1356024355.62450.YahooMailNeo@web161303.mail.bf1.yahoo.com" target="_blank">1356024355.62450.<u></u>YahooMailNeo@web161303.mail.<u></u>bf1.yahoo.com</a>> <<a href="mailto:50D353AC.7050805@gmail.com" target="_blank">50D353AC.7050805@gmail.com</a>> <<a href="mailto:1356031420.31416.YahooMailNeo@web161305.mail.bf1.yahoo.com" target="_blank">1356031420.31416.<u></u>YahooMailNeo@web161305.mail.<u></u>bf1.yahoo.com</a>> <<a href="mailto:50D367AD.5060404@gmail.com" target="_blank">50D367AD.5060404@gmail.com</a>> <CAJbhyRFa8c=dSTO=<a href="mailto:YJ0-KugZrRyCnAyUn0-E-ZXuffDbDgtsJw@mail.gmail.com" target="_blank">YJ0-<u></u>KugZrRyCnAyUn0-E-<u></u>ZXuffDbDgtsJw@mail.gmail.com</a>> <<a href="mailto:1356033155.57936.YahooMailNeo@web161304.mail.bf1.yahoo.com" target="_blank">1356033155.57936.<u></u>YahooMailNeo@web161304.mail.<u></u>bf1.yahoo.com</a>> <CAJbhyRGWZcO+<u></u>GeaYHqvigTtD91v6YmWwZ_g=c=<a href="mailto:N3Ap8uf0%2BWoQ@mail.gmail.com" target="_blank">N3Ap<u></u>8uf0+WoQ@mail.gmail.com</a>> <042701cddef0$95988350$<u></u>c0c989f0$@<a href="http://usmedrec.com" target="_blank">usmedrec.com</a>> <010201cddef3$03d23760$<u></u>0b76a620$@com> <<a href="mailto:50D37FBD.6050801@krampe.se" target="_blank">50D37FBD.6050801@krampe.se</a>> <<a href="mailto:1356041703.74106.YahooMailNeo@web171205.mail.ir2.yahoo.com" target="_blank">1356041703.74106.<u></u>YahooMailNeo@web171205.mail.<u></u>ir2.yahoo.com</a>> <<a href="mailto:20121221163355.11645q2qbeo05rc3@gator167.hostgator.com" target="_blank">20121221163355.<u></u>11645q2qbeo05rc3@gator167.<u></u>hostgator.com</a>> <<a href="mailto:1356120970.29755.YahooMailNeo@web171203.mail.ir2.yahoo.com" target="_blank">1356120970.29755.<u></u>YahooMailNeo@web171203.mail.<u></u>ir2.yahoo.com</a>> <<a href="mailto:20121221174656.97991hj4lfz0kjb4@gator167.hostgator.com" target="_blank">20121221174656.<u></u>97991hj4lfz0kjb4@gator167.<u></u>hostgator.com</a>> <005b01cddfc6$42dc1290$<u></u>c89437b0$@<a href="http://usmedrec.com" target="_blank">usmedrec.com</a>><br>
In-Reply-To: <005b01cddfc6$42dc1290$<u></u>c89437b0$@<a href="http://usmedrec.com" target="_blank">usmedrec.com</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
Content-Transfer-Encoding: 8bit<div class="im"><br>
<br>
<br>
<br>
Hi Folks,<br>
<br>
Thanks for suggesting all this, Ron.<br>
(inline)<br>
<br></div>
Ron Teitelbaum wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I’m happy with the fragmentation. I wasn’t at the start of this conversation but I think I’m starting to appreciate it. I agree that the goals for each are a bit different and having separated achieving those goals is easier. We are building some new stuff and it seems that selecting the right fork for the right job “may” not have been possible without the split. There are a number of new developments coming, (in the VM, Spoon, Seaside, Cuis, EToys, …) and it’s possible that one big monolithic Squeak may have made it more difficult for all. It seems that we are closer to having split up the components then we had thought.<br>
<br>
</blockquote><div class="im">
<br>
I agree.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I know we cannot make everyone happy. It seems that the starting point which seems to me to be COG, is the common link that binds everything else. Let me know if you think that is wrong. If that is true then building Squeak, or Pharo, or Cuis from a single point seems like something that might help bring the communities back together. Will Github or SmalltalkHub help to accomplish this? If this were a goal would either do more than the other?<br>
<br>
</blockquote>
<br>
I believe that the option that allows for a minimal image that can grow is something close to the package support in Cuis, that is extremely compact, doesn't require Monticello and relies on Github (or similar) for version control. I like the idea of building each distribution from a single point. That single point could be not far from current Cuis. I believe that Cuis, removing Morphic, programming tools, and any other non-kernel image or Cuis specific stuff, could become that single point.<br>
<br>
If the people behind other Squeak distributions and Squeak derived projects want to go ahead with this, I volunteer for building that starting point by removing from Cuis any stuff that anybody doesn't want in there. Then, the Cuis distribution would be built by loading a set of packages on top of it. The same could be done for the projects that adhere to this idea. Some of those packages could be shared. For instance, for Cuis, I'd be more than happy to use the Compiler package that Eliot works on. But, most likely, I'd not use the same Morphic package as Squeak. This could reduce the effort due to code duplication.<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I agree with the goal, we want to be able to load a package and have it work and it would be nice if the dependencies were limited/managed such so that it will load in any fork. Not all packages will load in every fork so knowing which will work beforehand is preferable. VW is different since nobody expects that with some work it will run on Oinq, I mean Cog (my name for the vm didn’t stick).<br>
<br>
</blockquote>
<br>
Qwaq for the voice of the duck, and Oinq for the pig, right? :)<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It seems to me that it doesn’t really matter. There seems to be some movement behind Metacello and SmalltalkHub. Sometimes movement is preferable to good ideas. If Metacello works for Squeak and will work with SmalltalkHub should we not include it in Squeak to give it a boost? If Squeak goes with GitHub will Pharo follow?<br>
<br>
</blockquote><div class="im">
<br>
Cuis doesn't include Monticello. I believe that a more compact and simpler implementation of package support, together with Github for version control, repositories, etc. is better. We are already using this with Cuis, and the results are good. It would be quite improbable that I could be persuaded of pre-loading Monticello into Cuis.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Nobody likes change but if we would all benefit from adopting some similar tools should we not consider doing that for the benefit of the entire Smalltalk community.<br>
<br>
</blockquote>
<br>
Agreed. Especially if it helps making the system (Cuis in my case) simpler, easy to understand, and manage.<br>
<br>
Cheers,<br>
Juan Vuletich<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All the best,<br>
<br>
*Ron Teitelbaum*<br>
<br>
/Head Of Engineering/<br>
<br>
*3d Immersive Collaboration Consulting*<br>
<br>
<a href="mailto:ron@3dicc.com" target="_blank">ron@3dicc.com</a> <mailto:<a href="mailto:ron@3dicc.com" target="_blank">ron@3dicc.com</a>><br>
<br>
Follow Me On Twitter: @RonTeitelbaum <<a href="https://twitter.com/RonTeitelbaum" target="_blank">https://twitter.com/<u></u>RonTeitelbaum</a>><br>
<br>
<a href="http://www.3dicc.com" target="_blank">www.3dicc.com</a> <<a href="http://www.3dicc.com/" target="_blank">http://www.3dicc.com/</a>><br>
<br>
3d ICC on G+ <<a href="https://plus.google.com/u/0/b/108936249366287171125/108936249366287171125/posts" target="_blank">https://plus.google.com/u/0/<u></u>b/108936249366287171125/<u></u>108936249366287171125/posts</a>><br>
<br>
*From:* <a href="mailto:squeak-dev-bounces@lists.squeakfoundation.org" target="_blank">squeak-dev-bounces@lists.<u></u>squeakfoundation.org</a> [mailto:<a href="mailto:squeak-dev-bounces@lists.squeakfoundation.org" target="_blank">squeak-dev-bounces@<u></u>lists.squeakfoundation.org</a>] *On Behalf Of *Juan Vuletich (mail lists)<br>
*Sent:* Friday, December 21, 2012 3:47 PM<br>
*To:* dimitris chloupis; The general-purpose Squeak developers list<br>
*Subject:* Re: [squeak-dev] Squeaksource, Squeak and Pharo..<div class="im"><br>
<br>
Cuis is reasonably compatible with Squeak. It has a distinct set of objectives, so some decisions are taken differently. Please see <a href="http://www.jvuletich.org/Cuis/Index.html" target="_blank">http://www.jvuletich.org/Cuis/<u></u>Index.html</a> .<br>
<br>
Maybe after some time with the various Smalltalk variants you get used to that fragmentation, and believe there are reasons for it. Or maybe you can help find the means to reduce that fragmentation.<br>
<br>
Cheers,<br>
<br>
Juan Vuletich<br>
<br></div><div class="im">
Quoting dimitris chloupis <<a href="mailto:thekilon@yahoo.co.uk" target="_blank">thekilon@yahoo.co.uk</a> <mailto:<a href="mailto:thekilon@yahoo.co.uk" target="_blank">thekilon@yahoo.co.uk</a>>><u></u>:<br>
<br>
Thank you. I am definetly going to take a look at Cuis. How<br>
compatible is Cuis to Squeak ?<br>
<br>
By the way I am already using Github for my first smalltalk<br>
(pharo) project which I call "Ephestos", together with ss3 as a<br>
backup plan.<br>
<br>
I dont do much with git , just the usual stuff, git push commit<br>
pull rm add .<br>
<br>
I have to say, the smalltalk field is abit confusing to me as a<br>
beginner, there is squeak , then there is pharo , then there is<br>
Cuis, etc etc<br>
<br>
Its a pity there is so much fragmentation. I am sure for some<br>
people this kind of freedome is cool and fun , but I personally<br>
try find ways to make things work together.<br>
<br>
But I have loads of fun with pharo , and definitely my eye is on<br>
Squeak too. I love smalltalk I wish I had discovered it earlier.<br>
But better late than never I guess :D<br>
<br></div>
------------------------------<u></u>------------------------------<u></u>------------<br>
<br>
*From:* Juan Vuletich (mail lists) <<a href="mailto:juanlists@jvuletich.org" target="_blank">juanlists@jvuletich.org</a><br>
<mailto:<a href="mailto:juanlists@jvuletich.org" target="_blank">juanlists@jvuletich.<u></u>org</a>>><br>
*To:* dimitris chloupis <<a href="mailto:thekilon@yahoo.co.uk" target="_blank">thekilon@yahoo.co.uk</a><br>
<mailto:<a href="mailto:thekilon@yahoo.co.uk" target="_blank">thekilon@yahoo.co.uk</a>>><u></u>; The general-purpose Squeak<br>
developers list <<a href="mailto:squeak-dev@lists.squeakfoundation.org" target="_blank">squeak-dev@lists.<u></u>squeakfoundation.org</a><br>
<mailto:<a href="mailto:squeak-dev@lists.squeakfoundation.org" target="_blank">squeak-dev@lists.<u></u>squeakfoundation.org</a>>><br>
*Sent:* Friday, 21 December 2012, 21:33<br>
*Subject:* Re: [squeak-dev] Squeaksource, Squeak and Pharo..<div class="im"><br>
<br>
Hi Dimitris,<br>
<br>
With Cuis, we use Github as the main place for storing packages.<br>
We use git as it is intended to be used. This means that we let<br>
git handle file versioning. Besides, Cuis uses lf as the line<br>
terminator. This means that git can diff and merge Cuis packages.<br>
For example see<br>
<br>
<a href="https://github.com/pbella/Cuis-Ports/commit/d2c70f95b6efee4f4d7671f432b4b304b5115c1d" target="_blank">https://github.com/pbella/<u></u>Cuis-Ports/commit/<u></u>d2c70f95b6efee4f4d7671f432b4b3<u></u>04b5115c1d</a><br>
.<br>
<br>
Cheers,<br>
<br>
Juan Vuletich<br>
<br>
Quoting dimitris chloupis <<a href="mailto:thekilon@yahoo.co.uk" target="_blank">thekilon@yahoo.co.uk</a><br></div>
<mailto:<a href="mailto:thekilon@yahoo.co.uk" target="_blank">thekilon@yahoo.co.uk</a>>><u></u>:<div class="im"><br>
<br>
SqueakMap is dead, SqueakSource dead, later SmalltalkHub will<br>
be dead.<br>
<br>
I am coming from pharo by the way, I am new with smalltalk, I<br>
was a python developer.<br>
<br>
And I love squeak too.<br>
<br>
I dont understand why every smalltalk problem should be solved<br>
by smalltalk.<br>
<br>
Github is a great community , already has gathered tons of<br>
ruby and python projects, js and many more.<br>
<br>
I think its a great candidate for smalltalk, no offense<br>
intended but definitely better that what SmalltalkHub can offer.<br>
<br>
I want to embrace at times all these smalltalk technologies,<br>
but is hard to abandon Gihub that I have used for my projects<br>
and support the smalltalk solutions instead.<br>
<br>
I dont want to downgrade the hard work of good people, but its<br>
hard to compete with products that are designed full time by<br>
big teams and matured through thousands of use cases.<br>
<br>
My vote goes to Github.<br>
<br></div>
------------------------------<u></u>------------------------------<u></u>------------<br>
<br>
*From:* Göran Krampe <<a href="mailto:goran@krampe.se" target="_blank">goran@krampe.se</a> <mailto:<a href="mailto:goran@krampe.se" target="_blank">goran@krampe.se</a>>><br>
*To:* The general-purpose Squeak developers list<br>
<<a href="mailto:squeak-dev@lists.squeakfoundation.org" target="_blank">squeak-dev@lists.<u></u>squeakfoundation.org</a><br>
<mailto:<a href="mailto:squeak-dev@lists.squeakfoundation.org" target="_blank">squeak-dev@lists.<u></u>squeakfoundation.org</a>>><br>
*Sent:* Thursday, 20 December 2012, 23:14<br>
*Subject:* Re: [squeak-dev] Squeaksource, Squeak and Pharo..<div><div class="h5"><br>
<br>
<br>
Hi folks!<br>
<br>
As the author of SqueakMap, long time Squeaker (and nowadays<br>
both Squeaker and Pharooner) and also involved in some other<br>
related projects (SmalltalkHub and more) my view might be of<br>
some interest.<br>
<br>
First of all, Angel compares with the rest of the world - but<br>
we have both historic and technical differences at play. Some<br>
things worth noting:<br>
<br>
- SqueakMap was indeed started out as a generic package<br>
*catalog*. It is not a SCM tool. It was format agnostic from<br>
the very beginning.<br>
<br>
- Monticello and SqueakSource came from Avi. Superb tools but<br>
when Squeaksource came I quickly warned the community that it<br>
would deminish SqueakMap because it overlapped and "took over"<br>
several "catalog" aspects. I was right unfortunately, but at<br>
the same time SS was great and has served us very well in its<br>
own right.<br>
<br>
- Noone has really taken SM and moved it forward. I also don't<br>
have that amount of free time anymore.<br>
<br>
- SqueakMap is dead. Face it. :) It is not the future IMHO.<br>
<br>
- Monticello and Metacello are the de facto standard these<br>
days for SCM and package loading. Metacello took the whole<br>
dependencies/tagging/releases issue and simply rode on MC to<br>
solve it. I have felt it looks overly complex but it's mostly<br>
some line noise - it is not that complicated.<br>
<br>
- This also means that for a very, very long time package<br>
management and source code management will be forever<br>
"intertwined" in the Smalltalk world. Personally I say - fine!<br>
Again, let's just embrace it and go.<br>
<br>
- The advantage is that Metacello "configurations" is "just<br>
code" and can offer functionality totally independent of the<br>
hosting platform for MC. So it doesn't matter if you load a<br>
Metacello configuration from a website, from SS or SS3 or<br>
Smalltalkhub - it all works the same!<br>
<br>
- Monticello AND Metacello are meant to work in Squeak too. I<br>
haven't tried, but I presume Metacello works or is very close<br>
to working?<br>
<br>
- Pharo is betting hard on Smalltalkhub. It is a really nice<br>
system AND there is also an image side client tool brewing for<br>
it! This means the equivalence of the SqueakMap Package Loader<br>
will be easy to build in Squeak for Smalltalkhub.<br>
<br>
<br>
So my advice would be:<br>
<br>
1. Keep SqueakMap on oxygen for a little while longer while we<br>
get ready to ditch it. Really.<br>
<br>
2. Bet hard on Monticello (we already do, right?) and<br>
Metacello for Squeak. Make sure they work. Embrace Metacello<br>
even if it does look a bit complex to begin with. There are<br>
lots of articles, tutorials and tons of examples to just copy<br>
from. I have written two configurations these last two days<br>
and "the shit works". Good work Dale! :)<br>
<br>
3. Get involved in Smalltalkhub and help out making it work<br>
fine for Squeak, note the name - *Smalltalk* hub. It's not<br>
Pharohub! Don't set up your own unless for some odd reason<br>
Pharo makes it uninhabitable for Squeak and turns it into<br>
"Pharohub".<br>
<br>
Note that Smalltalkhub is "just" a new SS, but much more solid<br>
architecture, really snazzy modern web UI, offering githubish<br>
features and bloody hell, I mean, it can show diffs right<br>
there in the browser!<br>
<br>
Smalltalkhub also has a really cool architecture so the coding<br>
fun is rated A++, Nicolas is busy as a bee making it better,<br>
better. I think it should be seen as a unifying playground and<br>
Metacello as the "glue" that makes it possible to have<br>
projects tailored for both Squeak and Pharo. It has many<br>
functions for EXACTLY that.<br>
<br>
Either way, I am putting my efforts right there. IMHO the<br>
Squeak community should do so too. If the Squeak community can<br>
ride a bit on the momentum in Pharo - there is really no<br>
reason not to.<br>
<br>
regards, Göran<br>
<br>
<br>
</div></div></blockquote>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Cuis mailing list<br>
<a href="mailto:Cuis@jvuletich.org" target="_blank">Cuis@jvuletich.org</a><br>
<a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/<u></u>listinfo/cuis_jvuletich.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>============================================<br>Germán S. Arduino <gsa @ <a href="http://arsol.net" target="_blank">arsol.net</a>> Twitter: garduino<br>Arduino Software <a href="http://www.arduinosoftware.com" target="_blank">http://www.arduinosoftware.com</a><br>
PasswordsPro <a href="http://www.passwordspro.com" target="_blank">http://www.passwordspro.com</a><br><a href="http://greensecure.blogspot.com" target="_blank">greensecure.blogspot.com</a> <a href="http://germanarduino.blogspot.com" target="_blank">germanarduino.blogspot.com</a><br>
============================================