Anders Hejlsberg

I think early on, we decided that we want to have a team of people design this language, not just...

I was sort of the guy who ran the group of designers, but we put together a group of six people or so, six, seven people.

And we got in a room three times a week for two hours and just started the design, you know, like literally that start from the top.

What is the, we all knew what, I mean, these were all people who had built or worked on programming languages before.

right?

And, and had seen all of the things you're supposed to do and all the things you're not supposed to do.

And quite honestly, language design is 90% the same and 10% new for, for pretty much every language.

Every language you build still has to have a compiler.

Compiler is still built in pretty much the same way.

And of course, as time marched on, people demand more and more.

You have to have IDEs, you have to have frameworks, you

blah, blah, blah, blah, blah, you know, and it's all there.

So there's a lot of experience you want to pull in.

And there's a lot of work that you're doing that isn't really per se new.

Um, but, but, but every time around you, you try to fix the problems that you've been exposed to.

This language design group worked together for years on end.

And it was lovely to come into work with a new idea and then immediately have five or six people that you could sit down and have a deep discussion with without first having to spend an hour level setting.

Do you, do you know what I mean?

Yeah.

Yeah.