[Master feature] TypeScript in AMP

[dreamofabear]

Add TypeScript support to AMP and allow new extensions to be written in TypeScript.

Motivation

Given the increasing maturity and popularity of TypeScript and potential developer productivity benefits, we'd like to experiment with TypeScript support in AMP.

Requirements

• Supports existing toolchain, particularly Closure Compiler usage
• Supports piecemeal adoption (with a rollback plan in case this I2I is rejected)

Proposal

1. Experiment: Allow new extensions to be written in TypeScript, which will be transpiled to Closure-annotated JS via tsickle as a preprocess to our normal compilation pipeline.
2. Gather data: Ship at least one new AMP extension written in TypeScript and collate pros/cons of development experience. Survey AMP community on TypeScript vs. JavaScript preferences.
3. Convert: If gathered data is supportive, add support for incremental transpilation for remaining source and convert existing JS to TS file-by-file.

[dreamofabear]

/cc @kristoferbaxter @cramforce @rsimha @erwinmombay @jridgewell

[cramforce]

I wish I had done this July 22nd 2015 :)

[dreamofabear]

Everyone, please fill out the public preliminary interest survey! 🙏

[dreamofabear]

Overall:
~15% disapprove, ~20% undecided and over 60% approve.

Positive sentiment:
Static typing should yield better productivity and less buggy code.

Negative sentiment:
Concerns about TS's longevity, learning curve, and opportunity cost of code migration.

See full survey results.