Purpose of classical approach | Relationship to object state
<p>There is a library written purely using objects literals to group similar items.  This is some what related to having public static classes.  For example</p>

<pre><code>var public_statics = {
    var1 : 'hello',
    func1 : function(){//stuff}
};
</code></pre>

<p>I see that people write OO ( or similar) JavaScript by emulating classes or simply using new on JavaScript function objects.</p>

<p>In web(I've heard this on SO and experienced it), it seems there is not much state.   What I mean by this, is you never seem to have 2 different objects from the same "class".  </p>

<p>For example I have a UserNew model "class" in which it is only possible to have one model at any given time.  In fact all of my models are this way, there is only one instance at any given time.</p>

<p>Are there any examples of state-full applications ( where you instantiate multiple objects )?</p>

<p>Am I perhaps building out this library wrong if all the models are collections of public statics using object literals?</p>

<p>I can post any code that might be relevant.</p>
