that would be very good

And also in sayHello. And in the interface. this._name and this.name... Makes me think..?

It works because the getter and setter are defined for name

Because if you then want to create a class that inherits from Call, you will have inherited the method `getName()` but not the private variable it's accessing, since it's neither attached to the prototype, nor the constructor.

Would create a confusing situation where you have a base class with a private method that's not inherited to sub-classes because it's private-via-closure and not on the prototype.

A subclass is not supposed to inherit the private methods of its superclass.

+Alex Leung The issue is classes may have public methods, but those public methods can use private variables. So the inherited version of that method is trying to use something that wasn't inherited alongside it. Could lead to nasty runtime errors.

I disagree. When inheriting a superclass, the methods on the superclass object are closures with references to private properties within the superclass itself, so the subclass methods cannot reference these private members but the superclass methods still can. Still not convinced? Here's a super simple working example I whipped up. github.com/AlexLeung/typescript_could_inherit_with_scoping Compare example_ts.ts to example_js.js After compiling example_ts.ts and opening index.html, you'll notice that not only do both files implement inheritance, but both also produce the same output when given identical tests.

The issue with example_js.js now is the accessor methods to the private variables aren't defined on the prototype anymore. So the "class" method will actually return true on a "hasOwnProperty" check of an instance of that class. Its important to keep in mind that the TypeScript "class" keyword needs to follow the ES-future spec of the class keyword. So that's a deal-breaker. jsbin.com/kehuwakica/edit?html,js,console

It's because angular2 has complete typescript implementation. so these lines '"import {Component} from 'angular2/core' just import them as is, written in pure typescript. Reference links are as i understand for typescript type hinting got from *.d.ts files generated from javascript libraries if you haven't specified tsconfig.json to allow typescript compiler look to source files as a project. take a look at definitelytyped.org/ - definition files for js libraries.

No you're not missing anything. That way is perfectly legitimate when the function that you are calling supports it. Most APIs are not built that way.

what about the bind method? (function(){this;}.bind(thisArg)); or call() or apply() There seems to be a lot of tools on native JS that are being under-appreciated... but I admit, they can be verbose and ugly to OCD eyes. Anyways, this TypeScript looks fabulous and I want to try it out ASAP. Thanks