If you get to a point where you have to optimize loops to shave milliseconds, neither library is going to offer you any advantages/disadvantages, you've walked in no man's land and it's back to straight _javascript_ fundamentals.
Where proto shines is the clean class based OO style and the lexical scope preservation abstractions. You will not have problems with it's performance, and like I said, if you are, then YUI will be no better for your app.
PS: Don't worry about not using RoR... I'm a .NET guy and have never written a lick of Ruby.
On 7/20/06, Brian Feliciano <
[EMAIL PROTECTED]> wrote:
When you say "most likelty end up being very close in performance" are you favoring the yui way or the proto way?
i am about to create a js app based on prototype and i am really concerned about speed and performance.
(i am almost feel awkward posting this to a rails community, since i'm not user. forgive me :D )
btw, thanks brandon.On 7/20/06, Brandon Aaron <[EMAIL PROTECTED]> wrote:They will most likely end up being very close in performance but I find the prototype/scriptaculous to be more programmer friendly.
Brandon
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
_______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
