Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
On the front page for MooTools, it says:
MooTools code respects strict standards and doesn’t throw any warnings.
I like MooTools, but having recently read The art of throwing JavaScript errors, I’m a bit confused as to why ‘not throwing any warnings’ is a feature. If a library doesn’t tell you when there’s an error (which may be caused because you are using it incorrectly), how are you going to fix the problem?
Why wouldn’t you want a library to throw errors?
Thanks,
Steve
Some javascript frameworks throw warnings due to rules being bent to achieve cross-browser support. I believe that MooTools’ claim is that they don’t throw any warnings to the browser in that sense, as opposed to the you doing something wrong with it sense.
e.g. http://groups.google.com/group/jquery-dev/browse_thread/thread/f2926d95fcafb18