What are your arguments?
I have some arguments to back up my idea:
1. Compiler emitted metadata
Since using these features can help corporations to save money it is likely that we will engage this new features really soon.
We are going to need metadata but who is going to write it? The idea is that developers will not have to write this metadata themselves and the compiler will generate the metadata for us. I don’t see myself thinking every morning “I can’t wait to get to the office and spend 8 hours writing metadata!” so I believe that we will use a compiler.
2. Compilation security
Compilation-time errors can prevent us from dealing with many potential run-time errors. As we know run-time errors is something that we will potentially deal with during the maintenance phase of a project and that’s where most of the cost of developing a software product is allocated.
3. Compilation optimizations
Good application performance could save a lot of money in infrastructure to your organization and (sadly or not) if something can be used by corporations to save some money then it is unstoppable.
However, I won’t dare to attempt to predict how long we will be using TypeScript for.
UPDATE (18 June 2015)
Techcrunch.com just published the following headline:
Google, Microsoft, Mozilla And Others Team Up To Launch WebAssembly, A New Binary Format For The Web.
In a few years I believe all the top browsers will sport JS engines that have become truly polyglot virtual machines.
UPDATE (19 June 2015)
Investigating about WebAssembly I have found two interesting talks about the rise of the compilers:
- Rise of the Transpilers by Jeremy Ashkenas
- ECMAScript Harmony: Rise of the Compilers - Brendan Eich keynote
UPDATE (9 October 2015)
Another interesting new related with this topic:
The TypeScript team have started looking at what it might take to pass through your TypeScript code so it can be emitted in strong mode.