TypeScript Updated to 1.0.1
Many developers are unhappy that future releases won't be supported on Visual Studio 2012 and earlier.
Microsoft's TypeScript has been bumped from version 1.0 to 1.0.1, and includes a new limitation that's rankling some developers.
On the TypeScript blog, Ryan Cavanaugh said that the minor upgrade mainly fixed issues with performance, stability and Visual Studio 2012 compatibility. It was the last item that caused some consternation. "The TypeScript 1.0.1 release will be the final release supported on Visual Studio 2012," Cavanaugh wrote. "This will allow us to make the next TypeScript a more full-featured development experience in future releases."
That explanation didn't sit well with some posters. "I suggest to consider not dropping VS2012 support, as most people I know still use it," said @jonathanAdunlap. "This could be viewed negatively as a way to get everyone to upgrade, unless there's a better stated reason than the blanket "a more full-featured development experience."
"Joe" had similar concerns. "Dropping 2012 support does seem very sudden... Does this mean that VS2013 will share the same fate when 2014 is out?"
"James Wilkins" said Microsoft should at least delay the decision: "Considering companies rarely update on the "bleeding edge", it takes time for them to evaluate and upgrade. By now, perhaps many companies are moving/have moved to VS2012, and suddenly now this wrench is thrown in - I'm guessing not a smart move at all." Most of the comments were in a similar vein.
Not everyone agreed, though. @markrendle said: "VS2012 people: you're going to have to upgrade at some point. The longer you leave it, the harder it gets."
TypeScript 1.0.1 is available through numerous avenues: as part of Visual Studio 2013 Update 2, released Monday, as a Visual Studio 2012 power tool, source code on CodePlex, or as an npm package. As of the time of publishing, Microsoft had not responded directly to the complaints.
Keith Ward is the editor in chief of Virtualization & Cloud Review. Follow him on Twitter @VirtReviewKeith.