> > Unfortunately, that will pretty much guarantee suboptimal code. For > almost anything nontrivial, it is probably worth writing your own JS. >
Optimization is a game of compromises I'd say - you have readability/maintainability/speed of development on one hand and "performance" of the code itself on the other - timing/memory etc. If I understand it right, ruby language and rails framework tends to weight the first category more - and that is where my advice comes from. But you are right...if you know for sure that you are going to run a particular version of a particular browser, you might as well spend all the time to figure out all the JS special functions provided by that JS engine and squeeze out every bit of power. Regards, Kashyap --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
