Re: [Axiom-developer] RE: [M#73697383] Re: Disk-quota Request

[root]

> > any system that considers 20M to be 'huge' needs a rethink.
> >
> 
> The term "monstrously huge" is being used in a relative sense, i.e. 80
> megs of .zip files is big compared to a typical tree of source code.
> 
> There's no limit to the size of files that can be uploaded/downloaded.
>  It's HTTP.  The whole system was designed to be 'streamy' with large
> files.
> 
> CVS, on the other hand, requires that the server hold the entire
> tree-being-checked-out in RAM.  If you do a checkout of 400 megs of
> source, your server better have 400 megs of RAM to hold it.  If 5
> people are checking out that source tree at once, your server better
> have 2 gigs.  Not so scalable.

so the 'video documentation' that i'm currently building for axiom
has no hope of being supported? it's the late 90s and i figure that
it's time to consider using video tools to enhance the axiom tutorial.
these video clips are another way to explore literate programming.
even with compression these files regularly top 20M.

the 'src/video' directory will likely hold between a CD and a DVD
worth of mini-tutorial topics. these can be added and deleted in
small, section-sized segments as they get modified with better
information. they will be an integral part of the axiom src distribution.

i'm not alone in testing this direction. the lisp SLIME project
has their tutorial done in video. camtasia has their tutorials in
video.

does it make sense to rely on a version control system that fails
to handle 20M files? 

perhaps CVS/SVN needs a bit of redesign to handle the future.

t