Sorry for breaking the stream. I could not find the email with
thunderbird :(
Just for the record, you see what netstyle people did: they use image
segment and they had to kill everything (like processes and others)
because of
possible pointers so after saving a segment the image was basically dead
because some escaping pointers to make a kind of memory leak.
Now they migrated to Fuel.
So now I think that people should better use Fuel. IS were nice at first
but not when you look carefully to them, especially when you have
an object not in the roots pointing to an object inside the graph. Then
you have to do a GC…. Mariano spent a year fighting with that
and his PhD is really nice.
Less magic, more stability, simpler VMs.
Because all the energy that you will put in something from the past will
not be put in things for the future(not counting the bug hunting).
Stef
On Mon, Oct 20, 2014 at 8:26 AM, stepharo <[email protected]> wrote:
While I as a big fan of imageSegment and proposed to mariano to work on
imageSegment2 (it was the original idea for his phd)
he convinced us that imagesegment were not worth their complexity.
I absolutely agree.
So why do you want to have imageSegment?
Because of backwards-compatibility. If Spur does not provide image
segments then the barrier to entry for Terf, eToys and Squeak may be too
high. Spur is supposed to be a plug-in replacement for Cog, not
something that requires lots of effort to port to
