On Dec 10, 9:15 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 10, 2008 at 8:44 AM, mabshoff
>
>
>
> <[EMAIL PROTECTED]> wrote:
>
> >> A Sage build is over a gigabyte, involves well over 5 million lines of
> >> code, and is probably bigger than any other single math software
> >> system in the world. And amazingly we're doing fine size-wise. I
> >> think we can handle a few more hundreds of pages of hand-written
> >> Python code.
>
> > Yes, the secret goal here is world domination after all ;)
>
> > But I think Moore's law will protect us from ever growing faster in
> > relative terms than the computer's average ability. Just compare the
> > size of recent Sage releases and you will see that the average growth
> > rate of the tarball is slowing down. And if we ever reach a colossal
> > size that makes development cease or significantly slow down we can
> > always consider creating a smaller core of Sage for those who want it.
>
> We can also do an "audit" and cut out bits that aren't used or needed anymore.
> e.g., quaddouble.
Yep, for me the next library on the chopping block will be symmetrica
unless the relationship with upstream drastically improves (or someone
mean would call that "exist"). clisp is on its way out and is being
replaced by ecl, but other than that there is nothing else in Sage I
would consider myself to be unhappy about.
Wit the extcode as well as documentation reorg we will drop a couple
MB each, so the 3.3 release will probably be below 200 MB for the
source distribution again.
>
> -- William
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
