Jamie Kyle

How do we want to handle this? Because React has a different code path for these types of components which will instantiate a class.

> Second, we invoke the the Component instead of newing it. We could new, but that's a throw-away object every time we render. I thought React worked by holding onto...

Yeah, I would sooner monkey patch iDOM than native objects.

Isn't the element returned on `close` not open?

I like the basic concept here, it'd be cool to explore

How far is this from reality?

Also 6to5: http://6to5.github.io/

You could do: ``` js class MyView extends Backbone.View { constructor() { super({ tagName: 'h1' }); this.el.textContent = 'Hello World'; } } ```

@milesj that's still not allowed when you are subclassing. @jridgewell Oh sorry, I missed that. It does seem like the most natural option. I spoke to jeffmo and sebmck about...

@milesj As stated before ES7 class properties do not solve this issue as they aren't instantiated until the end of the constructor. I spoke to jeffmo and sebmck about doing...