And to reiterate something... using a minifier and gzip, it becomes
something like ~14.5kb, which is like serving up a decent rez jpg thumbnail
image, which is like nothing. And if you're using Ajax you should be able to
minimize the number of times the lib needs to be served to a given
application space... and just to drive this whole thing further into the
ground, you should be sure your libs are being cached appropriately by the
browser, which of course makes the whole size thing even less of an issue
for subsequent requests to your application.
On 3/28/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote:
> On 3/28/07, Eric Harrison <[EMAIL PROTECTED]> wrote:
> > Unfortunately, the problem here
> > is that Prototype.js gets all of its power and smallish size by using
> > it's own functions extensively throughout the code.
> Eric gave a very good answer. Modules in Prototype framework can hardly be
> decoupled since they heavily depend on each other. BUT, I've been
> researching how to automate slimmed-down builds of Prototype, too - not for
> real world usage, but as a proof-of-concept.
> In real world you could take out a part of Prototype you don't use, but
> would want to put it back sooner or later. There is no part of Prototype
> that isn't useful for every-day usage.
Application Development Consultant
Athena Group, Inc.
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at