This project has moved and is read-only. For the latest updates, please go here.

JSLINQ Object Vs Array.Prototype

Feb 7, 2010 at 1:14 AM

Before I ask my question I just want to say; really nice job with this project. It's simple, elegant, and makes a lot of JavaScript developers lives a lot easier!

Now onto the question.
I'm curious to know why you decided to use a new object, "JSLINQ", rather then 'extend' on the existing Array object using the prototype approach? This question isn't an insult on your approach because it works, I was just wondering if you had considered the .prototype approach, and then for some reason changed your mind?

keep up the good works.

Oct 25, 2010 at 12:48 PM

JSLINQ resides in its own object so that it does not conflict with any other javascript frameworks you might be using. This is the same reason that jQuery resides completely within its own "jQuery" object instead of extending the core javascript objects with certain functionality.