I think I'm still getting angry comments on that post.
How the World Changed
How I Changed
This Column and the Immediate Future
You just can't make some people happy, I guess.
It seems to me that there's only one way to find out how I feel about TypeScript: build something. So, I'm going to use TypeScript to build what I'd consider a client-side LOB application. I'll use something familiar: a single page that allows the user to select a customer and see all the sales orders for that customer. The user can then add, update or delete any of the sales orders. My expectations are that I'll be able to use TypeScript to create an MVVM structure within my page; that I'll be able to integrate with the libraries that I normally use (including Knockout and QUnit); and that I'll be able to communicate with the server using both older tools (Windows Communication Foundation [WCF]) and newer tools (the Web API).
This is early innings for getting started with TypeScript -- it's not yet at version 1.0, for instance. There are also some significant constraints if you want to use it in Visual Studio: it's currently only supported in Visual Studio 2012 and, even then, only for C# projects. If you want to use TypeScript outside those bounds, you can download a command-line compiler from Node.js. But TypeScript is an important enough technology to make it worthwhile to start examining it early in its life.
And, starting next month, that's what I'm going to do.
Peter Vogel is a principal in PH&V Information Services, specializing in ASP.NET development with expertise in SOA, XML, database, and user interface design. His most recent book ("rtfm*") is on writing effective user manuals, and his blog on technical writing can be found at rtfmphvis.blogspot.com.