That's an interesting approach, however, it is not the equivalent of the hybrid constructor/prototype inheritance approach. First,
doesn't actually do anything. The delete operator is used only to delete properties on an object, not the object itself. Second, you are creating a second object the first time the constructor is called, which forces the developer to effectively call the constructor twice instead of once.
Thanks for the feedback, but I don't believe you've disproved my statement.
Nicholas C. Zakas