lol, lazy devs
Um, 'easier to analyze' doesn't mean "lazy devs"... I happen to have a little background in programming, and
trust me:
any simplification you can introduce to a complex program during the debug process can
easily make the difference between finding a bug, and having to re-write the broken code from scratch to try and get it right
this time. And the latter is, obviously, not a very good idea for a project as big as this one.
Ron
What about in this situation
"Ooops..."And SINS is saving a 350mb file each time it autosaves? Granted in the finished product the files might be compressed a little, but surely a limit on the number of files to save would be a good option to include.
In that case, be
glad that terabyte sized hard drives are coming closer and closer to being the norm
Just out of curiosity, what happens when Sins
doesn't have the room to save anymore? Does it go "boom"?
And just to clarify my position a little, I do
not object to controls that limit how much HD space goes to Autosaves, what I
do oppose is any approach that cannot be controlled by the end-user. Approaches involving limiting the number of saves (up to infinity) the total size used by saves (up to infinity) and the total percent of HD used by autosaves (up to 100%) would all be acceptable -- especially if we get all three
