Anders Hejlsberg

And to be frank, something that could compete with Java, right?

And so that's why we started out building C Sharp.

Well, like I said, I mean, the overarching thing was this power and productivity of C++ with the ease of use of visual basing in a sense, right?

But what it also meant was we knew we wanted to build an object-oriented language.

We wanted managed code or byte code so we could target different runtime environments.

We wanted garbage collection and exception handling, but also things like a unified object system where

And that's true in C sharp.

Like anything can be assigned to an object.

And if it's a value type, we box it.

And it's a self-describing object.

So reflection, you can ask an object, what are you?

And you can get all of the facts about it at runtime.

And you can dynamically manipulate it in ways that just don't exist in a lot of other environments.

And we knew we wanted to go there with that.

We wanted a language that made sense.

this new model of properties, methods, and events first class, because that was how components were built as opposed to just sort of functions and procedures and even objects, right?

And then we actually also wanted to create a language that was standardized.

We wanted to give this language to a standardization committee and try to

you know, level the playing field there.

And all of those things were sort of like what was rolled up in C sharp.