<div dir="ltr"><div><div>Yes, Pharo is doing a great work of simplification.<br></div>On the other hand, it deliberately has zero requirements to make removed parts reloadable, so the task is a bit easier...<br></div></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">2013/10/25 Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 24 October 2013 22:02, Edgar J. De Cleene <<a href="mailto:edgardec2005@gmail.com">edgardec2005@gmail.com</a>> wrote:<br>
><br>
><br>
><br>
> On 7/28/13 3:22 PM, "Frank Shearar" <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>> wrote:<br>
><br>
>> It's a term I picked up from work: SqueakTrunk is like a dessicated,<br>
>> dried out thing that's quite small, like a dessicated pea. But<br>
>> ReleaseSqueakTrunk is like the rehydrated pea, useful for cooking.<br>
>><br>
>> As the package layering work proceeds, and more packages become<br>
>> unloadable, I unload them from SqueakTrunk. ReleaseSqueakTrunk takes<br>
>> that small SqueakTrunk artifact and reloads all those unloadable<br>
>> packages.<br>
>><br>
>> The idea is that people just keep on using the ReleaseSqueakTrunk<br>
>> image, and without even realising it, are using a _constructed_ image,<br>
>> built up from some small core.<br>
>><br>
>> frank<br>
><br>
><br>
> And when we go bold and use a Core.image?<br>
> Our cousins Pharoers build a PharoKernel from sources , great work of Pavel<br>
> and Guillermo (and others maybe).<br>
<br>
When I have time, basically. I reconstructed the base image from<br>
scratch recently, and haven't had a chance to re-rip out Nebraska,<br>
Universes, and all the other bits I'd previously removed.<br>
<br>
I'm very happy to see Pharo do this work. Kudos to Pavel & Guille & friends!<br>
<br>
frank<br>
<br>
> Edgar<br>
><br>
><br>
><br>
<br>
</blockquote></div><br></div>