# byte based quota

Susan Garfinkel (sgarfink@dept.english.upenn.edu)
Mon, 30 Oct 1995 15:09:29 PST

- Messages sorted by:[ date ][ thread ][ subject ][ author ]

    perhaps i'm in the minority, but i prefer the object based quota for a new
    moo, especially if the switchover is easy. my reasoning is that we want to
    encourage people to make full use of the potential of an object-oriented
    environment, and one object that's fully described (@chparented, messages
    customized, etc.) and does some neat stuff (people have a reason to learn
    programming) is better than 10 objects that we all affectionately refer to
    as "tiny scenery". you know, if it doesn't do anything, it doesn't need
    to be a separate object... i guess it depends on your goals for the moo,
    if you want to encourage rich texture or if anything goes as long as it
    doesn't get too big. perhaps the ideal solution is to put a cap on both
    number of objects, and total byte size.

    if you do switch the default in a next release, please be sure to leave
    object-based quota as an option for those who want it.

    sg.