Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Ever heard of Script#? Us neither, and that's probably a good thing. Anders Hejlsberg, creator of Turbo Pascal and Delphi, the lead architect of C#, and the designer of TypeScript, talks about how TypeScript came about from a need for "grown-up tooling" and the question "How can we fix... show more

GitHub

2,672,396 subscribers

36,036 views • 7 months ago •via X (Twitter)

Education Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

TypeScript was inspired by a strange ask from the outlook team. Anders Hejlsberg(Anders Hejlsberg) - creator of C#, TypeScript, Turbo Pascal & Delphi - tells us how TypeScript was born: “The world started building larger and larger applications in JavaScript. We saw that externally, but also internally. One of the trigger events was when the outlook team came to see the C# team and asked us whether we would pretty please productize this thing called Script#. And we go, well, what is Script#? It's this cross compiler that allows you to cross compile C# into JavaScript such that you can basically treat JavaScript as an instruction language and run your C# apps in a browser. Why would anyone want to do that? Well, because then you can get a grownup programming language with grownup tooling. You can use Visual Studio, you can have projects. You can do all of these wonderful things that you can't do with JavaScript because JavaScript is just the scripting language with shitty tooling. And we thought, well, perhaps a better approach would be to fix JavaScript. I mean, surely you're not going to be best of breed in the JavaScript ecosystem by telling people to write in a different programming language”

TypeScript was inspired by a strange ask from the outlook team. Anders Hejlsberg(Anders Hejlsberg) - creator of C#, TypeScript, Turbo Pascal & Delphi - tells us how TypeScript was born: “The world started building larger and larger applications in JavaScript. We saw that externally, but also internally. One of the trigger events was when the outlook team came to see the C# team and asked us whether we would pretty please productize this thing called Script#. And we go, well, what is Script#? It's this cross compiler that allows you to cross compile C# into JavaScript such that you can basically treat JavaScript as an instruction language and run your C# apps in a browser. Why would anyone want to do that? Well, because then you can get a grownup programming language with grownup tooling. You can use Visual Studio, you can have projects. You can do all of these wonderful things that you can't do with JavaScript because JavaScript is just the scripting language with shitty tooling. And we thought, well, perhaps a better approach would be to fix JavaScript. I mean, surely you're not going to be best of breed in the JavaScript ecosystem by telling people to write in a different programming language”

The Pragmatic Engineer

116,193 views • 3 months ago

The best thing about building in the open? Nothing gets lost. Anders Hejlsberg, creator of TypeScript and C#, on 12 years of issues and decisions, all searchable. "It didn't just disappear into some email I can't find anymore." Take a trip down memory lane and tell us: what was your first open source contribution?

The best thing about building in the open? Nothing gets lost. Anders Hejlsberg, creator of TypeScript and C#, on 12 years of issues and decisions, all searchable. "It didn't just disappear into some email I can't find anymore." Take a trip down memory lane and tell us: what was your first open source contribution?

GitHub

35,772 views • 1 month ago

On this week’s GitHub Podcast, we talked about how Typescript became the #1 programming language on GitHub. Now hear from the creator, Anders Hejlsberg. 👀 Get his thoughts on this year’s Octoverse findings. 💭⬇️

On this week’s GitHub Podcast, we talked about how Typescript became the #1 programming language on GitHub. Now hear from the creator, Anders Hejlsberg. 👀 Get his thoughts on this year’s Octoverse findings. 💭⬇️

GitHub

30,986 views • 9 months ago

"Find the stuff that's boring and uninteresting, but you know still costs you, and try to get AI to do that for you." TypeScript's creator, Anders Hejlsberg, on how AI should get rid of all the toil you deal with when coding. Watch the full interview.

"Find the stuff that's boring and uninteresting, but you know still costs you, and try to get AI to do that for you." TypeScript's creator, Anders Hejlsberg, on how AI should get rid of all the toil you deal with when coding. Watch the full interview.

GitHub

40,734 views • 4 months ago

Announcing: From zero to Turbo! 🎉 Learn the fundamentals of JavaScript and TypeScript monorepos - and how to make them fast. Will post all of the series on X and on YouTube in a playlist. First up: How to structure a monorepo. ↓ YouTube link in thread. Like 'n' subscribe!

Announcing: From zero to Turbo! 🎉 Learn the fundamentals of JavaScript and TypeScript monorepos - and how to make them fast. Will post all of the series on X and on YouTube in a playlist. First up: How to structure a monorepo. ↓ YouTube link in thread. Like 'n' subscribe!

Anthony Shew

23,984 views • 2 years ago

Anders Hejlsberg (Anders Hejlsberg) is a living legend: he created Turbo Pascal, Delphi, C# and TypeScript (and today TypeScript is the most-used programming language, globally, as per GitHub.) Timestamps: 00:00 Intro 02:48 How Anders got into programming 05:40 Building his first compiler 07:44 Turbo Pascal 12:25 Delphi 14:53 Joining Microsoft 19:41 Building C# 29:11 Async/await 34:01 The rise of JavaScript 37:52 Building TypeScript 42:58 How the TypeScript compiler works 48:30 JavaScript’s strengths and weaknesses 52:18 How Anders uses AI 56:03 What language features work well with AI 1:02:49 How software craftsmanship is changing 1:07:49 Performance and efficiency 1:09:29 Anders’ tool stack 1:11:30 A 30-year career at Microsoft 1:13:40 Book recommendation Brought to you by: Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. WorkOS – Everything you need to make your app enterprise ready. turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. Four things that stood out to me: 1. “10x better for 1/10th of the price” is a proven winner. This is what Turbo Pascal did: it sold for $49.95 when competing compilers cost $500, and it was faster and more interactive than competitors’ products. Conveniently, the low price tag also killed off piracy 2. C# might have not existed without a famous court case. Microsoft originally hired Anders to architect its Java tools (Visual J++), but the Sun versus Microsoft lawsuit (1997-2001) meant Microsoft could not build on top of Java, as the company that owned Java’s IP (Sun) sued MS for alleged unauthorized changes to the Java language. Microsoft realized it had to build a new language that combined VB’s productivity with C++’s power. This led to C# and .NET. 3. TypeScript exists because Anders refused to build Script# for the Outlook .com team. Microsoft’s Outlook .com team asked Anders’ C# team to productize “ScriptSharp,” a language to cross-compile C# to JavaScript. Anders and the C# team pushed back, suggesting that a better approach was to fix JavaScript. Anders felt strongly that to be attractive to the best-of-breed developers in the JavaScript ecosystem, you want people to write JavaScript, and not another language like C#. 4. Designing a programming language is a 10-year play. As Anders puts it: “Version one is great, but has all sorts of issues. You’ve got to do version two, but it’s not until version three that it really starts to be great. Then you’ve got to convince people to adopt it.”

Anders Hejlsberg (Anders Hejlsberg) is a living legend: he created Turbo Pascal, Delphi, C# and TypeScript (and today TypeScript is the most-used programming language, globally, as per GitHub.) Timestamps: 00:00 Intro 02:48 How Anders got into programming 05:40 Building his first compiler 07:44 Turbo Pascal 12:25 Delphi 14:53 Joining Microsoft 19:41 Building C# 29:11 Async/await 34:01 The rise of JavaScript 37:52 Building TypeScript 42:58 How the TypeScript compiler works 48:30 JavaScript’s strengths and weaknesses 52:18 How Anders uses AI 56:03 What language features work well with AI 1:02:49 How software craftsmanship is changing 1:07:49 Performance and efficiency 1:09:29 Anders’ tool stack 1:11:30 A 30-year career at Microsoft 1:13:40 Book recommendation Brought to you by: Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. WorkOS – Everything you need to make your app enterprise ready. turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. Four things that stood out to me: 1. “10x better for 1/10th of the price” is a proven winner. This is what Turbo Pascal did: it sold for $49.95 when competing compilers cost $500, and it was faster and more interactive than competitors’ products. Conveniently, the low price tag also killed off piracy 2. C# might have not existed without a famous court case. Microsoft originally hired Anders to architect its Java tools (Visual J++), but the Sun versus Microsoft lawsuit (1997-2001) meant Microsoft could not build on top of Java, as the company that owned Java’s IP (Sun) sued MS for alleged unauthorized changes to the Java language. Microsoft realized it had to build a new language that combined VB’s productivity with C++’s power. This led to C# and .NET. 3. TypeScript exists because Anders refused to build Script# for the Outlook .com team. Microsoft’s Outlook .com team asked Anders’ C# team to productize “ScriptSharp,” a language to cross-compile C# to JavaScript. Anders and the C# team pushed back, suggesting that a better approach was to fix JavaScript. Anders felt strongly that to be attractive to the best-of-breed developers in the JavaScript ecosystem, you want people to write JavaScript, and not another language like C#. 4. Designing a programming language is a 10-year play. As Anders puts it: “Version one is great, but has all sorts of issues. You’ve got to do version two, but it’s not until version three that it really starts to be great. Then you’ve got to convince people to adopt it.”

Gergely Orosz

129,459 views • 3 months ago

Kishore Mahbubani talks about the west and how they lack understanding of whats happening in the world. A very good question and a very good answer.

Kishore Mahbubani talks about the west and how they lack understanding of whats happening in the world. A very good question and a very good answer.

Johannes Maria

518,694 views • 2 years ago

How do we make software more secure for all of us? Log4Shell proved that open source security isn’t guaranteed and isn’t just a code problem. It’s about supporting, enabling, and empowering the people behind the projects that build our digital infrastructure. Watch the full interview with Log4J maintainer Christian Grobmeier:

How do we make software more secure for all of us? Log4Shell proved that open source security isn’t guaranteed and isn’t just a code problem. It’s about supporting, enabling, and empowering the people behind the projects that build our digital infrastructure. Watch the full interview with Log4J maintainer Christian Grobmeier:

GitHub

17,955 views • 8 months ago

Creator of C#, Anders Hejlsberg(Anders Hejlsberg), on the design goals that shaped the language and why standardisation was a goal from the beginning: “The overarching thing was this power and productivity of C++ with the ease of use of Visual Basic. 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#, anything can be assigned to an object. 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. We wanted a language that made 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. And we wanted to create a language that was standardised. We wanted to give this language to a standardisation committee and try to level the playing field there. And all of those things were sort of like what was rolled up in C#”

Creator of C#, Anders Hejlsberg(Anders Hejlsberg), on the design goals that shaped the language and why standardisation was a goal from the beginning: “The overarching thing was this power and productivity of C++ with the ease of use of Visual Basic. 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#, anything can be assigned to an object. 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. We wanted a language that made 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. And we wanted to create a language that was standardised. We wanted to give this language to a standardisation committee and try to level the playing field there. And all of those things were sort of like what was rolled up in C#”

The Pragmatic Engineer

18,332 views • 3 months ago

On Colours of Fire (out in December), I think we are about to see cinema like never before, Niyi talks about the work ethics of Uzor and how incorporating our culture into art and the doggedness of artisans. You can watch the full interview here:

On Colours of Fire (out in December), I think we are about to see cinema like never before, Niyi talks about the work ethics of Uzor and how incorporating our culture into art and the doggedness of artisans. You can watch the full interview here:

Ibi Divine Doo ♥️💜

10,902 views • 9 months ago

Here's a conversation with Evan You, creator of Vue and Vite ⚡. A brilliant mind, and one of the greatest JavaScript developers in the history of programming. We talked about Vue, Vite, Nuxt, Vercel, and VoidZero. Watch here:

Here's a conversation with Evan You, creator of Vue and Vite ⚡. A brilliant mind, and one of the greatest JavaScript developers in the history of programming. We talked about Vue, Vite, Nuxt, Vercel, and VoidZero. Watch here:

nunomaduro.php

29,400 views • 11 months ago

Why Microsoft didn't have LLMs do their recent Typescript native rewrite in Go Anders Hejlsberg (Creator of Typescript): "If we just let AI loose on, what is it, half a million lines of code that we have in the old compiler? Well, I don't know that that would absolve us from then having go in and carefully examining every line that came out of it to make sure that there were no hallucinations. Right. Unless you have 100% perfect test coverage, you probably still gotta go check all of that. Now I think a better approach, quite honestly, would be enlist AI to write a program that helps you translate from TypeScript to go, because at that point you can park the stochastic ness in that program and then you can get deterministic behavior whenever you run the program, which means you get the same transformation every time you run it. Right. That's always the thing about AI that people forget it's not deterministic. Right. So you can't really trust that it's going to do the same thing twice. For the full conversation, you can search Anders Hejlsberg's name on my YouTube, Spotify or Apple Podcasts (link in bio)

Why Microsoft didn't have LLMs do their recent Typescript native rewrite in Go Anders Hejlsberg (Creator of Typescript): "If we just let AI loose on, what is it, half a million lines of code that we have in the old compiler? Well, I don't know that that would absolve us from then having go in and carefully examining every line that came out of it to make sure that there were no hallucinations. Right. Unless you have 100% perfect test coverage, you probably still gotta go check all of that. Now I think a better approach, quite honestly, would be enlist AI to write a program that helps you translate from TypeScript to go, because at that point you can park the stochastic ness in that program and then you can get deterministic behavior whenever you run the program, which means you get the same transformation every time you run it. Right. That's always the thing about AI that people forget it's not deterministic. Right. So you can't really trust that it's going to do the same thing twice. For the full conversation, you can search Anders Hejlsberg's name on my YouTube, Spotify or Apple Podcasts (link in bio)

Ryan Peterman

83,672 views • 6 days ago

Anders Hejlsberg ( Anders Hejlsberg ) is the creator of TypeScript and C#, and I asked him about how the TypeScript compiler got 10x faster through a rewrite in Go and his thoughts on how AI has impacted software engineering. In this episode: • How rewriting the compiler makes it 10x faster • Why they picked Go instead of Rust • Why they didn't use LLMs for the migration • Predictions on AI's impact on software engineering Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - Thank you to the sponsors of this episode for supporting my work: • WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at • Jira by Atlassian: Get more work done with your favorite agents and models all in one place, check them out at Chapters: 00:00 Intro 00:48 Why write a compiler in JavaScript 07:29 Why rewrite the compiler in Go 14:49 LLMs for large migrations 20:12 Why Javascript is so popular 26:32 Why ever use Javascript on the backend 32:59 What it takes to build a programming language 37:06 Will there be fewer languages in 10 years 42:57 Hands on engineering vs delegation 49:14 Why fast tooling matters more now 51:16 AI software engineering predictions 58:52 The most technically challenging work 01:02:04 Top book recommendation 01:03:50 Advice for his younger self 01:05:00 Outro

Anders Hejlsberg ( Anders Hejlsberg ) is the creator of TypeScript and C#, and I asked him about how the TypeScript compiler got 10x faster through a rewrite in Go and his thoughts on how AI has impacted software engineering. In this episode: • How rewriting the compiler makes it 10x faster • Why they picked Go instead of Rust • Why they didn't use LLMs for the migration • Predictions on AI's impact on software engineering Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - Thank you to the sponsors of this episode for supporting my work: • WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at • Jira by Atlassian: Get more work done with your favorite agents and models all in one place, check them out at Chapters: 00:00 Intro 00:48 Why write a compiler in JavaScript 07:29 Why rewrite the compiler in Go 14:49 LLMs for large migrations 20:12 Why Javascript is so popular 26:32 Why ever use Javascript on the backend 32:59 What it takes to build a programming language 37:06 Will there be fewer languages in 10 years 42:57 Hands on engineering vs delegation 49:14 Why fast tooling matters more now 51:16 AI software engineering predictions 58:52 The most technically challenging work 01:02:04 Top book recommendation 01:03:50 Advice for his younger self 01:05:00 Outro

Ryan Peterman

60,350 views • 10 days ago

We’re chasing the outrage of the day while a tidal wave of tech change reshapes wages, productivity, and inequality. Can we please have the grown‑up conversation about how to harness AI for broadly shared prosperity?

We’re chasing the outrage of the day while a tidal wave of tech change reshapes wages, productivity, and inequality. Can we please have the grown‑up conversation about how to harness AI for broadly shared prosperity?

Justin Wolfers

18,627 views • 9 months ago

In a new Sakura interview on abema she talks about her members She talks about how Emily is so positive and bright 🥹 And she talks about how she grew closer to Lexie 🦋,how they went out for shopping and food talking about the future of the group She also highlights her love for Samara

In a new Sakura interview on abema she talks about her members She talks about how Emily is so positive and bright 🥹 And she talks about how she grew closer to Lexie 🦋,how they went out for shopping and food talking about the future of the group She also highlights her love for Samara

SAINT SATINE CRAVE🗞️🪽🤍🖤

146,947 views • 3 months ago

Kelly talks about how Beyoncé was writing records and producing vocals in an interview from the dawn of the 21st century.

Kelly talks about how Beyoncé was writing records and producing vocals in an interview from the dawn of the 21st century.

BEY-Z

14,053 views • 9 months ago

wonwoo and jeonghan talking about how their unit came together 🐈 the company wanted to try out a fun unit so they recommended the [combination of] the both of us 😇 since both of our characters are different, they put both of us together to see what kind of album would come out. so upon discussing... there are a lot of urban legends right? we thought about those one by one as a concept and that's how the album came about

wonwoo and jeonghan talking about how their unit came together 🐈 the company wanted to try out a fun unit so they recommended the [combination of] the both of us 😇 since both of our characters are different, they put both of us together to see what kind of album would come out. so upon discussing... there are a lot of urban legends right? we thought about those one by one as a concept and that's how the album came about

🎮

40,604 views • 2 years ago