Anders Hejlsberg

And that goes back even to the predecessor of Turbo Pascal, this idea that it's not just a compiler.

It's an experience, right?

I mean, you don't just compile your programs.

You also edit them.

You also run them.

You also debug them.

You also have a runtime library.

It all has to like fit together.

You know what I mean?

And so Turbo Pascal was always about building that whole cycle and try to make it as interactive as, as, as basic was as an interpreted language, right?

But giving you the performance of a compiled language and the better, you know, semantics and syntax of, of, of, of

a Pascal versus basic.

And so that was sort of the idea from day one, you know, focus on the whole cycle.

You know, the first versions of Turbo Pascal didn't have a debugger.

You know, you would just use right-link statements and then you'd just see what happened, right?

But often, if you had some error and it blew up with a runtime error, we would print out the address of the runtime error, which is where was the program counter at that point.

And then we had a mode in the compiler where we would say, compile, but stop at this address.

And so the compiler was real simple.

It would just produce object code.

And then once it hit that address, it would just say, well, whatever I'm syntactically looking at right now, that must have been around where the error was.