> For less sophisticated developers (most people, and most of the VS
> market), the compiler errors will remove much debugging frustration and
> allow them to focus on creating rather than debugging.
>
>
It also allows them to focus on "creating" instead of understanding what
they are doing. Take the sample on the playground for instance:
constructor (message: string) {
this.greeting = message;
}
will translate to:
function Greeter(message) {
this.greeting = message;
}
If you can only handle string, should you not be doing a check and writing
a proper message? What will happen to javascript users that consume your
code generated with TypeScript? It's not a huge gain IMO, and a few CONS:
- only get intellisense in VS (a gigantic IDE which will handle from
databases, to manual tests).
- TypeScript seems to be making the code longer to type and less readable
instead of shorter/better (like others do).
- yet another language/dependency on your project.
- most of the type-related things could be handled gracefully with comments.
Gus
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
