On Mon, Apr 9, 2012 at 8:52 PM, Jonathan S. Shapiro <[email protected]> wrote:
> The simple explanation is that Tarditi's analysis of tree shaking was naive. > Systemic performance at multiple levels of abstraction demands code sharing > across programs. But the fundamental assumption of whole-program compilation > is that no code sharing across programs will result. I don't know much of anything about singularity, and this I suppose may be the crux of 'tree shaking', but this discussion leads to a lingering question i've had about capability os's in general, since in a capability os executables appear to have a tighter focus, and programs tend to be made of multiple executables, and the entry point(s) to programs not being simply character based it would appear to encourage more whole-program reuse, increased whole-program reuse would seem to mitigate the need for shared libraries, but i've never really tried to answer whether it would be enough to tip the balance. though I surmise from your position you consider the answer to be 'no', I just wanted to make sure that was a 'No, not even under conditions favourable to whole-program reuse.' _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
