Part 1 -Getting Classy
With that in mind, let's dive in by introducing one of the basics that will help keep your code organized.
Get Object Oriented
That is the easiest way to just group a bunch of variables into a class. It's quick and easy but has some downsides to keep an eye out for. If you need to make a lot of these you're going to have to type that out a lot which could lead to fat-fingering it some place. There's also the fact that the `speak()` function we created is an instance variable on each object, which means it will take up more memory than if we defined it in the more classical prototype fashion that would share the function across objects.
The classical prototype way is a little more verbose, but it comes with the benefit that we now have a way to really pump out some `Baby` objects if we needed to. Notice the way we use `this` in the constructor to make instance variables on the object (more on the magic of `this` in another post.
My rule of thumb is to use the quick and dirty way when I'm making a "one off" object that is just temporary and won't have many instantiations.
I try to be strict about using the classical approach when I'm creating something that will have more than one instance of itself in my app.
Next time, we'll talk about closures and some of the ways we can keep our newly created objects from banging into each other in the global scope.
Now Playing - The American Dollar - Anything You Synthesize