On Nov 4, 2013, at 13:32 , Anne van Kesteren <[email protected]> wrote:
> Objects not having constructors is a bad API practice we are moving away from. I'm not sure everybody thinks so. There are whole libraries out there that avoid the use of 'new' in favor of functions that create the objects for you (e.g. Two.js, Raphael.js, etc). Douglas Crockford amongst others is advocating against the use of 'new' for a long time. We're used to calling document.createElement(), etc. To me it feels strange that all of a sudden, browser provided functionality is not bound to a context, but is implemented by such a free-floating constructor.
