Published on August 03, 2012 by Toran Billups
I quickly found that you can create a class-like-object the same way you create a function (because classes don't exist in the language). But what I found interesting is that depending on who you ask ... some people use the 'new' keyword when they do this and some people don't. So I decided to find out why this new keyword was so important.
In the first example I create a human using the new keyword and then I try to print the property that is set at the time the object is constructed.
That works like you would expect, but what if we leave off the new keyword?
This time around it blew up when we tried to print the property because 'this' was 'undefined' for some odd reason. It turns out that the new keyword actually provides some context for the function as it's executed. We can simulate this (long hand) using the apply function. First you pass in the context manually (the human object), next you pass in the array of arguments that will be passed to the function as it's invoked.
You can achieve the same result using the call function, the only difference is that instead of an array for the second param you can pass in any number of arguments and they will be passed along to the function as it's invoked.
So next time you think about leaving off the 'new' keyword ... think about the context you are leaving out