I agree with Dhugal. We are(were?) evaluating Sencha for a big project and that a seemingly official representative of Sencha was making those dismissive comments is disturbing and bad for Sencha's business.
Whether people like it or not, Coffescript, Typescript, and a whole bunch of other languages that compile down to Javascript are not going away. If COBOL was the only game in town for the browser, we'd be compiling down to that too.
If Sencha embraces these other languages, then they're more likely to not lose business when other toolkits come out for Typescript.
This is my first result, don't know if it really works runtime, but at least I get no compiler errors anymore .
Maybe the documentation can be added to. (so you can get JS documentation text in Visual Studio).
Well done. I tried learn ruby to extend JSDuck, but a I gave up. Its a nice idea to load files as json in .NET. I will try to generate a Ext3.4 definition.
Come on Sencha you do not have a spare year to think about TypeScript, it is happening right now, look at all the JavaScript libraries already converted for TypeScript:
I also find the "ugly" term a little offensive as one must understand that Typescript is an attempt to add type to a totally unstructured little language that took 2 weeks to write! Intellisense is just one part of the problem as one of really painfull aspects of Javascript is that typos can cause the developer to waste so much time. Any tool that can help in this area is an asset to me and especially given that the architect of the compiler is Anders Hejlsberg, the architect of C#.
Now I also like the "improvements" that Sencha has been adding to JS but Typescript is a huge step above these. I am also playing with Typescript support for Ext and hope that we can find a solution. Sencha would be foolish to not look at this impressive tool that could change how Javascript is written.