Anyway, I'm not sure your theories are even close to being better. If Safari uses the system wide rendering engine, then Safari simply does not have a rendering engine of its own. And if you never installed safari, the system wide rendering engine would still be there. So, by adding the system wide rendering engine to the size of Safari is simply false representation.
I dont think so, webcore and javascriptcore, altho not in safari's folder, is not used by OSX as a fundamental system-wide structure. I think calling it system wide engine, is a misrepresentation of its usage in OSX.
not to mention gecko as an engine also being used by other apps, email client, browsers, music manager, sketch production, etc.
if we were to compare browser size, we can't exclude engine.
Webkit is 99% a browser engine, call it system wide doesn't make it more useful in osx other than a dictionary, a email client, a help system maybe.
more importantly,
there is no significant addition into webkit for it to perform tasks outside a browser.
IE is different, its so tightly bundled into system, every windows explorer is an IE shell, and desktop. Webkit is NOT that tightly bundled in OSX.
This shows that Apple is actively attempting to reduce the size of their software, where possible. The latest developer version of OS X, Snow Leopard also further illustrates this. A clean install of the latest developer release of 10.6 consumes significantly less space than a clean install of 10.5 Leopard.
first i applaud the good development.
second, is SL intel only? if so, size reduction is a natural result, which I think our tiger and leopard users should have enjoyed that 2 years ago.
this is another example of apple...mmm.. lets soften it a bit, ...not putting size as a propor priority. For intel only macs with Tiger and Leopard, users are wasting GB space.
in which sense do you think 80Mb and 53MB smaller than 46Mb?