On 11/29/06, Andrew Dupont <[EMAIL PROTECTED]> wrote: > > On Nov 29, 10:16 pm, "Peter Michaux" <[EMAIL PROTECTED]> wrote: > > Choosing a library is much more than a simple matter of taste. > > You've lost me here.
Choosing a library is complex. Is the library riddled with bugs? Can the library already do what you need it to do? Is the library written in a way that makes extension easy? Does the library have documentation? > > I am not better equiped to decide than you. I want to providing an > > alternative to people using Rails that don't like Prototype. > > You need to re-read the stuff you've written in this thread. You've > suggested that choosing Prototype over another framework is > "unfortunate," and you've done so without qualifiers, so I assume you > mean that as a blanket statement. "However, I think that choosing an library because it has a nice API but poor internals is an unfortunate choice." This is a general statement. For me it applies to Prototype. Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
