Sergey Nivens - Fotolia
TypeScript's co-creator speaks out on TypeScript 4.0
Luke Hoban, CTO at Seattle-based infrastructure-as-code platform provider Pulumi, co-created TypeScript while working at Microsoft.
In this Q&A, Hoban discusses the beginnings of TypeScript, the features he likes in the newly released TypeScript 4.0 and what he looks forward to in the future for the language.
At Microsoft, in addition to co-creating TypeScript with prominent coders Anders Hejlsberg and Steve Lucco, Hogan developed Go support for Visual Studio Code, was part of the design teams for ECMAScript and C#, and served as technical assistant to the corporate vice president of Microsoft's Developer Division.
Upon leaving Microsoft and prior to his role at Pulumi, Hoban did a stint at AWS, where he led product definition and business planning for EC2 instance families including GPU, field programmable gate arrays and T2 compute offerings.
What are your thoughts on the popularity of TypeScript?
Luke Hoban: It's been the fastest-growing programming language in the world for much of its life, and is now among the most used programming languages in the industry. The TypeScript team and community continue to execute exceedingly well on the vision and promise of TypeScript to this day. We are now seeing TypeScript lead a new generation of technologies, beyond just the browser and the server, as the primary language for the evolving modern cloud infrastructure management space.
Hoban: In 2010, Microsoft had many teams across the company, and especially in Office, moving toward building very rich web-based applications, not just the traditional websites. The engineers working on these projects were used to the tools and IDEs they used to manage software complexity on Windows -- with C++ and C# and Visual Studio -- and were struggling to manage the scale of the applications they wanted to deliver on the web.
What do you like about TypeScript 4.0?
Hoban: There are tons of great new language features that help unblock things for clearer and simpler APIs in 4.0. But the thing that I am most excited about is the focus on editor improvements. The value of TypeScript has always been most significant in the minute-to-minute experience inside an IDE or editor -- getting feedback about errors, hints on how to refactor code or help text to understand an API. [Version] 4.0 takes this further in several important directions, and provides these benefits to users in many IDEs -- from the Visual Studio family to a long list of other editors and IDEs.
How does TypeScript 4.0 help in terms of developer productivity and ease of use?
Luke HobanCTO, Pulumi
What could have been done better in TypeScript 4.0, or what was left out that should have been included?