Anders Hejlsberg

You know, there's open source and there's open development.

And we were technically open source in the beginning, but it was not open development.

We would sort of lop the source code out in this repository and scrape the issues off of that and put it into our internal issue tracker.

And then, you know, but once we switched to GitHub, the entire workflow moved to open development also.

And that, I love that.

this popular and of course we've had other languages python being the other very popular one but what captures developers preferences this well well i think you know it didn't just happen overnight you know and if you look back at that that you know all of a sudden we we surfaced as number 10 and then we climbed slowly over the years up and and and sat

next to JavaScript, right?

And of course, if you add a JavaScript and TypeScript together, then we were already number one.

It's just which syntax.

Were you using type annotations or not?

And more and more people

over time just decided to adopt that.

I mean, some early on were using JSDoc or whatever, you know, and like these types in comments or that we also supported.

But gradually, I think people just realized, hey, this is the right way to do it.

And the reason they came, I think, is absolutely because of the better tooling.

And I think we were totally right there that like adding an erasable type system and then

is written in TypeScript.

And so they were one of our earliest adopters, and we work pretty closely with them to this day.

That whole interplay, that in turn is also what led to the invention of LSP, the Language Server Protocol, that now pretty much every tool vendor uses to enable

interactive services in the IDE.