>> Except for a proxy bug which needs fixed, I'd love to know how youThere are lots of operations in the IDE that cause network accesses,
>> would possibly improve it even if you could do so by the mere snap of
>> your finger. Because I wanted the best of both worlds. I want 1) the
>> ability to clean / reduce an image, 2) WITHOUT losing the ability to
>> retrieve the ancestry. Oh, and 3) it'd be nice if I didn't have to do
>> a special UI operation to "retrieve the ancestry", just have the
>> system retrieve it automatically please only if I do something in the
>> IDE that requires it.
>>
>> Again, assuming all the proxy-bugs fixed, what more could one want in
>> terms of meeting all the demands we want as developers?
>
> How about not downloading megabytes of data from the network when I didn't
> tell it to do that?
and none of them advertise in advance that they'll access the network.
So this argument is not really a good one against.
> Proxies are aI think this is your best argument. I agree Proxies are a powerful
> useful tool, but they should be kept in the bottom of the toolbox and only
> used in special circumstances. The vanilla image shouldn't have proxies.
tool to be used sparingly with deliberate care, but it basically boils
down to using a become:, which we already use in numerous other places
in the image.