Current best-practice eschews the "new" keyword on Javascript primitives. If you want to create a new Array simply use brackets [] like this...



var myArray = [];


You don't need to tell Javascript how many items to size the Array for. Javascript will automatically increase the size of the Array as needed, as you add items into the Array. Creating an Array with brackets instead of with the "new" constructor avoids a bit of confusion where you want to initialize only one integer. For instance.







As you can see these two lines do two very different things. If you had wanted to add more than one item then badArray would be initialized correctly since Javascript would then be smart enough to know that you were initializing the array instead of stating how many elements you wanted to add.
Since the new constructor is not necessary with Arrays and there's a slight chance of unintended results by using the new constructor, it's recommended you not use "new Array()" to create an Array.

Usually when you see something like this:
arrayName.item(0)

it is referring to something in the DOM, for example:
http://jacksleight.com/blog/2008/01/14/getelementsby/

I'm sorry, I should have been more clear. Let's say I already did something like
var pageInputs = getElemetsByTagName("input"); Now, i have a collection, pageInputs. So what's the difference between
console.log(pageInputs[0]) and
console.log(pageInputs.item(0))
I haven't had a chance to test them, but wouldn't they return the same thing? I just hadn't seen the '.item()' syntax before.

R0bb0b is correct ... item(0) accesses a node-collection

as an example of different arrays / node collections

Yes, they would return the same thing and are effectively the same, but the .item(0) is the correct syntax for DOM node-collections, but the array access syntax is cross-browser supported.

...

Thank you folks, and thanks Langsor. That's what I was thinking, but just wanted to make sure.