[Pharo-users] BS Web and Pharo

[Tim Mackinnon]

Hey guys - when reading about the BS web (great article btw - 
https://pxlnv.com/blog/bullshit-web/ ) it reminded me about the constant 
pestering to sign up for the Pharo newsletter. 

Given I am signed up - how can I stop it always popping up? 

It’s in the list of the BS web... so do we really need it to do this? At least 
it should be a cookie that if I have it it goes away, or better still - just 
put it as a menu entry and let people sign up if they like out stuff?

Given our community fights the BS can't we lead better?

Tim

Sent from my iPhone

Re: [Pharo-users] transactions on pharo objects

[Esteban A. Maringolo]

El mié., 1 de ago. de 2018 20:52, Richard Sargent <
richard.sarg...@gemtalksystems.com> escribió:

> Esteban A. Maringolo wrote
> > As a general purpose solution if you can do that, you end up
> > implementing a mini gemstone in Pharo :)
> >
> > But what's sure is that you should have a mini object-table of the
> > "touched" objects or do "explicit" registration of these objects like
> > GLORP allows you to do.
>
>
> It seems to me that the fundamental problem with the idea of registering
> each object with the transaction (or anything else) is that it requires
> white-box knowledge of what every invoked behaviour will do and touch. The
> above example is so minimal, it looks easy.
>

I agree with that. Deciding when to what to copy and what to preserve is
always tricky unless yo decide to copy the whole object graph which would
be terrible. Very much like what to proxy and what to forward in GemBuilder.

I think if you really want transactional Smalltalk, you need to use one
> designed expressly for that purpose.
> (And fortunately, there is one.)
>

That's why I say this is tricky and you'll probably end up implementing a
mini-GemStone.

I don't know what it means in terms of programming, but having a
transactional object memory would be a useful thing to work with.

Regards,

Esteban.