Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)

I've posed the [dynamic class creation question on StackOverflow](http://stackoverflow.com/questions/40062815/how-do-i-create-ecmascript-classes-on-the-fly). People are pointing out the class expression, but it still statically defines what type to extend from, which is pertinent in the Schema.org example-case where there is deep nesting of classes: I'm back to typing 650 things out by hand.

I'd love for there to be a little more discussion- a start to there being shared knowledge about what couples to what that makes doing anything other than class impossible here- but I don't feel like I'm getting much traction. I'll try to follow up with TC39 and see if perhaps we can get some kind of Function that apes the new class. I suspect 99% of the problem here is just that class forces subclasses to call super(), which seems like a tragic reason to fork the language constructs like this, but I'm 99% less knowledgeable than Domenic here.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/587#issuecomment-254004864