I started using prototype a little while back as a permanent part of my [grossly mutated] version of DomBlog (cheers, Jake) and really like the speed it has added to coding changes and demos. Ain't that ajax support sweet?
Yeah, 40 kb? not really an issue these days. But, if it were, you could always try a script packer, or gzip if your server supports it. Probably get it down to 18 kb or so.
@ Scot
I also have a site we're working on that uses Rico and while it does a nice job, I wouldn't put it in the same class as prototype. It lacks the same level of polish. Just check out the rico home page in IE and FF and you'll spot some issues. Like Prototype, it also lacks documentation but proved much more sensitive to implement. It is cool enough, though, that we're going to go ahead and put it on a customers site for some visual effects.
I started using prototype a little while back as a permanent part of my [grossly mutated] version of DomBlog (cheers, Jake) and really like the speed it has added to coding changes and demos. Ain't that ajax support sweet?
Yeah, 40 kb? not really an issue these days. But, if it were, you could always try a script packer, or gzip if your server supports it. Probably get it down to 18 kb or so.
@ Scot
I also have a site we're working on that uses Rico and while it does a nice job, I wouldn't put it in the same class as prototype. It lacks the same level of polish. Just check out the rico home page in IE and FF and you'll spot some issues. Like Prototype, it also lacks documentation but proved much more sensitive to implement. It is cool enough, though, that we're going to go ahead and put it on a customers site for some visual effects.