> On 24 Nov 2014, at 21:29, Hilaire <[email protected]> wrote:
>
> Pharo 1.4 image = 15MB
> Pharo 3 image = 22MB
> Pharo4 image = 32MB
>
> Don't know about Pharo 2.0 as, skip it.
>
> Is there a limit?
Keeping mind that most of this is
-> some artefact of the build process that the stack is saved
open the image and save it
down to 31.2MB
-> the ScriptLoader package (with >123 KLOC now)
down to 25.5MB
-> Monticello meta data
down to 22.5MB
And this is even not what we will have for the release, as there is e.g. 500KB
of loreIpsum
strings in the image… that should be removed. (they are for testing the editor)
Now yes, there is more code in the image than for Pharo 1.4:
- Metacello. This is *HUGE*
- Versionner
- Kommitter
- OSWindow
- Rubrick editor + tests
- Glamour + GT with tests
- …...
22.5 MB is not a lot for all that.
Now this image has all tests and all tools. #cleanUpForProduction removes
Versionner and unloads all tests.
===> down to 17,8 MB
Not too bad!
Questions to ask:
- is 22MB really big? Many of the apps on my phone are *much* larger
than that.
Even very simple ones. People these days complain when phones come
with “only 1GB of RAM”.
- Time is on our side. Moore Law for storage says we can double every
year and stay constant.
And I am willing to invest that for more expressive power, at least
some years.
- If we would *really* care for space: Wouldn’t we start to e.g. start
to do thing like string sharing
and compression of some unused data?
As always: nothing happens by itself….
Marcus
