With class constructors, you are forced (not really, but it is strongly suggested) to do both construction and initialization in the same step.
I've never seen this "forcing" anywhere in a classical OOP language, and in fact there are thousands that have separate constructors and "init" methods.
What this guy doesn't realize is that he is using a "constructor" when he calls Object.create(). That is literally all constructors are supposed to do in classical OOP languages.
Share this highlighthttp://www.safaribooksonline.com/a/you-dont-know/14994300/