Anders Hejlsberg

in the real compiler and in the language service, right?

And so that ultimately led us to this project called Roslyn, where we built a single compiler that really is both, it's a compiler that can both function as a command line compiler and as an interactive service inside the IDE.

TypeScript is built that same way also, and there's a lot of learnings from doing it that way that are still not being taught in school.

Yeah.

I mean, luckily we had internal clients, the .NET Framework.

very quickly started implementing in C Sharp.

They had sort of used a hacked up version of C++ to implement, which was kind of odd because, I mean, it was like targeting bytecodes, but not really.

And so they switched to C Sharp and that helped a lot.

And then we had other internal teams using it.

And so we got a bunch of feedback that way.

And then we had, you know, the cycle was not that long, right?

I mean, I think we started in late 98.

And by the PDC of 2000, we signed up.

I mean, we basically gave away beta copies, right?

And got tons of users onto it.

Well, a lot of languages are built around cooperative multitasking in the sense that they have an event loop that sits and dispatches events.

And then, you know, you handle the event and then you yield back to the event handler loop.

And it all runs in a single thread cooperatively.

right?

The problem with that is if you then want to do some long running work, how do I stop in the middle of this piece of long running work and yield back to the event loop cooperatively, right?