- From: Jürg Lehni <lists@scratchdisk.com>
- Date: Wed, 6 Nov 2013 12:41:50 +0100
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: Juriy Zaytsev <kangax@gmail.com>, Rik Cabanier <cabanier@gmail.com>, "whatwg@lists.whatwg.org" <whatwg@lists.whatwg.org>, Simon Pieters <simonp@opera.com>, Dirk Schulze <dschulze@adobe.com>, Dean Jackson <dino@apple.com>, Ian Hickson <ian@hixie.ch>
On Nov 4, 2013, at 13:32 , Anne van Kesteren <annevk@annevk.nl> 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.
Received on Wednesday, 6 November 2013 11:42:25 UTC