alignment with es6 classes (prototype/instance properties)

In latest es6 spec is possible to define prototype properties as well as per-instance properties.
In typescript we can define only methods as prototype properties (or use ugly "out of class" definitions). I miss this feature a lot.
Someone says prototype properties will be confusing, but why?
In es6 prototype and instance properties are written differently in very "easy to understand" way.

I suspect we won't align completely before 1.0. There are some features, like class expressions, we don't yet support (though I believe we could in theory, we just haven't put the resources into it, yet). We'll likely explore more alignment post 1.0.

// The only way to create prototype data properties is by// modifying the prototype outside of the declaration.
Monster.prototype.numAttacks = 0;

This is what we currently get with TypeScript.

Personally, I cannot see any benefit in the monster example you have posted. That appears to be imposing a penalty on the more common usage (instance properties) and favouring a generally rare use-case (prototype properties).

If you have any common use cases for putting properties on the prototype then it should be interesting to see them.

@nabog , you are right. I saw on that page only what i wont and miss "superseded" message on top.
If es6 decided to use "Maximally Minimal Classes", my opinion is totally irrelevant.
Sorry for useless topic.

The ECMAScript 6 completion is (or at least was) a bit of a moving target. What we've opted to do, in the module case for example, was to try to align the syntax in a way that we could add in the ES6 features on top of the existing TypeScript ones. This
means we're picking minimal syntax in places with a lot of churn in the ES6 spec so we fill it out later once the ES6 spec is complete.