[Pharo-dev] [squeak-dev] Squeak and Tonel

Esteban Lorenzano estebanlm at gmail.com
Mon Feb 18 07:06:15 EST 2019


Hi, 

I’m so not wanting to be part of this discussion, but here I am. 
Just because it was mentioned my name in a way I consider inaccurate. 

> On 17 Feb 2019, at 21:27, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> 
> Hi All, Hi Torsten, Hi Jakob,
> 
> On Thu, Feb 14, 2019 at 6:17 AM Torsten Bergmann <astares at gmx.de <mailto:astares at gmx.de>> wrote:
> Hi,
> 
> as some of you might already know "Tonel" is a file-per-class format for monticello repositories [1].
> 
> In Pharo land many projects are already converted to it - as regular "file tree" solution faces issues 
> with git handling due to very long file names / deep file hierarchy (often leading to trouble on Windows).
> 
> Dales's Rowan (a new project/package manager for Smalltalk) supports FileTree and also Tonel 
> repositories [2]. There is also a tool to convert from STORE (VisualWorks Source-Code Versioning System) 
> to Tonel format [3].
> 
> So I wonder about adoption of Tonel in Squeak land. 
> 
> Any status/comments?
> 
> Last year I was given contract employment by Tudor Girba's feenk which in part was to involve me porting VMMaker.oscog to Pharo in order to reap the productivity benefits of the Glamorous Toolkit when applied to VMMaker.  The major direction was to unify the opensmalltalk-vm repository with a Toned-Format repository holding the Smalltalk code.
> 
> This project, though no fault of feenk's did not go well.  A big part of it was my own emotional attachment to Squeak, my "muscle memory" with Squeak and my long experience with Smalltalk-80 derived meta programming which I make extensive use of in VMMaker.oscog.  But a key issue was that I was not prepared to *move* VMMaker.oscog to Pharo; for me it is key that it can live in both places.  In particular I will not risk VMMaker.oscog being stranded on Pharo as it moves away from the "image-based rendering model".  This is not because I don't believe in pixel-independent rendering models, but because productivity in VMMaker depends much more than on GToolkit inspection on the key architectural feature of being completely, safely simulateable (not a real English word; but meaning capable of being simulated).  As Pharo moves towards external libraries to implement its UI so the degree to which VMMaker is simulated is reduced.  Thus crashes in external code cannot be handled with the same power as with errors presented within the Smalltalk environment itself, and this (as harsh experience over thirty five years has taught me) is far more important for overall productivity than having powerful tailorable inspectors.
> 
> I therefore wanted a Tonel that could both function for Squeak's Monticello and for Pharo's Iceberg.  I had modified the Tonel serialization a little to provide well-formatted support for method timestamps, which are still a key and extremely useful part of Squeak Monticello's "blame" equivalent.  Until git author attribution can be imported into Squeak's Monticello (something I don't see happening) I wanted merely to be able to have a variant of Tonel, enabled for example by a class variable, and hence /not/ present in Pharo, that would allow VMMaker.oscog to use Tonel but still be functional inside Squeak.  I asked Esteban and was met by a flat no.  Not "OK, but this is an option only you will use", but a flat "not under any circumstance”.

This is textually my answer (even with the English errors): 
… “Anyway the answer will be no :)
This was considered, and even the first implementation of tonel had it. Now, this was discarded because it does not works with git (or other file backends). It was not even me who complained first (as I said, I implemented it). It was Dale and other people used to work on git. 

Thing is,  putting timestamps it will generate conflicts massively when there is no reason to it.
So, we drop it… and we add support for  the equivalent using the tool we use (iceberg gives you not just the author that modified last the method but all of them, along the history).

I hope is an understandable reason?”

And then in other mail of same thread I suggested an approach viable for squeak: 

"Now, what I’m sure is that if you are trying of using the 100% of Monticello and to use git just as another repository backend, it will not work (we already tried). It will consume far too much effort and you will finish beating the purpose of use git and a file-based-format, and you will be in the worst of two worlds :)

We started like that, and we ended up implementing Iceberg to take benefit of the tools we are using.

In the middle, there was/is gitfiletree. 
(I think I suggested you to look at it to adapt it for tonel and squeak).

Gitfiletree uses OSProcess to call git as external tool and it makes all the operations needed. “


Now, what I was suggesting was a way to use tonel backed with OSProcess (which works in squeak) instead backing it with libgit2 as us. 
Since they need the blame support, they could use OSProcess and external git for it.

Of course squeak (and any other dialect) are free to take tonel and adapt it to their needs (in fact, Mariano extended Tonel for VA specific things). 
And Pharo can read that format but it will ignore all extensions. 
Now, another problem is to WRITE: Pharo would write those packages in “pharo format” and that information would be lost. And in the case of VMMaker, if the idea is to be able to work on both sides, then Pharo needs to “honour” that format, it cannot just read it and ignore it later. So this creates an incompatibility that needs to be handled. 

Anyway, as you can see my answer was not “not under any circumstances”. Was “no, because is not convenient”.

Esteban


> 
> So here I am joining in this thread reluctantly.  I'm extremely frustrated by the state of Tonel in Squeak and between the two dialects.  Clément had moved his Scorch optimizer to Tonel/git and I tried to use Metacello and Jakob's Tonel code to at least allow me to load that code and try and push forward on Sista/Scorch.  The port *does not work*.  Metacello fails to load Scorch.  Neither Jakob nor Fabio, after putting in some effort, were able to fix the problem, and it is well beyond me.  So I have accepted the fact that I will have to use the Monticello repository for Scorch/Sista.
> 
> I had deep concerns that the pursuit of git integration would end up splitting the Pharo and Squeak communities and indeed this is now in progress.  I am utterly unmotivated by the lack of cooperation, the sheer arrogance and bullying of those that say "you will move to git/tonel or else", and considering leaving VMMaker altogether.  The only things that are keeping me interested are Ron Teitelbaum's Terf and me pursuing a PhD on register allocation in the context of Sista/Scorch with Robert Hirshfeld's group at HPI.
> 
> Here's the kind of crap people like Ducasse throw at me:
> 
> "Eliot 
> 
> At the end of the day I will probably ask the two phds that should work on language design to use truffle or pypy
> because let us face it we cannot work with the Pharo VM. Else we will simply have to fork it (because we do not want to have 
> to jump over cuis, newspeak, squeak code constraints and I do not what) and it will be another drama is in the pico world 
> of the “open” smalltalk VM. "
> 
> I am so over this crap.
> _,,,^..^,,,_
> best, Eliot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20190218/e820aa17/attachment.html>


More information about the Pharo-dev mailing list