Seth Illgard wrote: > But why? Why prototype is THAT better? Doesn´t mootools has all the > functions and classes that prototype has?
Unlike a server-side library, JavaScript libraries are dreadfully hard to mix-and-match. Prototype's name derives from how it attaches prototypical methods to pre-existing JavaScript objects. Any other library which does that will conflict with Prototype, so there's generally only enough room in the hen house for one rooster. Next, Ruby on Rails wraps Prototype. So the checklist of benefits for Prototype must include a state-of-the-art full-stack web platform written in a fully OO language that makes very hard effects extremely easy to code. If you don't need a web platform, and if some other library has the features you need, by all means use it. -- Phlip http://www.greencheese.us/ZeekLand <-- NOT a blog!!! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
