<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>My two cents is that the profiler should be an external package that is brought into a minimal core at build time if desired. Now us the time to start doing that sort of thing otherwise it will be stuck in the base image and no one will know how to get it out.. The other packages as well of course, whether at build time for a release or as a later customization for individual users. <br><br>Ken,<div>from my iPhone</div></div><div><br>On 2013-01-25, at 11:22, Jeff Gonis <<a href="mailto:jeff.gonis@gmail.com">jeff.gonis@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>My quick two cents is that I agree wholeheartedly with Chris. There is tons of stuff in Morphic like Nebraska, Etoys and things like MVC and Universes that could be made Squeakmap packages before something like the profiler. These would also seem to give a far greater savings in terms of class count and LOC, than the comparatively small profiler.<br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 25, 2013 at 10:05 AM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ahem. Perhaps before we start slashing and cutting basic tools like<br>
the profiler, we should articulate a coherent description of our<br>
vision for a reduced image, what's in it, and what audience it would<br>
target.<br>
<br>
The profiler is an essential development tool, so that would seem to<br>
cut developers from the target audience. Whatever reason you want to<br>
cut it may be that you'd also like to cut the Process browser too -- I<br>
don't know without knowing what your goals are. Like everyone else I<br>
want a smaller image, but with "small" it should be more like a<br>
neutron star is to a red-giant -- *dense* with functionality and<br>
applicability. Until we can get to a truly "minimal" image (1MB) our<br>
cutting should be toward the goal of something Small and powerful, not<br>
small and useless. :)<br>
<br>
I suggest before we cut basic development tools we cut "app" type<br>
stuff like... "telemorphic" and<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On Thu, Jan 24, 2013 at 12:04 PM, tim Rowledge <<a href="mailto:tim@rowledge.org">tim@rowledge.org</a>> wrote:<br>
><br>
> On 24-01-2013, at 8:08 AM, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
><br>
>>> Chris, might I lean on you a bit to add a SqueakMap entry for the profiler?<br>
>><br>
>> Is this not something we should just put straight into the base image?<br>
>><br>
><br>
><br>
> I'd say no; and the existing one ought to be removed as well. Cut, slash, trim.<br>
><br>
> tim<br>
> --<br>
> tim Rowledge; <a href="mailto:tim@rowledge.org">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>
> "How many Kzin does it take to change a lightbulb?" "None. You can scream and leap in the dark."<br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span></span><br></div></blockquote></body></html>