Skip to content
0:00 / 0:00

#typescript#dart#javascript

Anders Hejlsberg and Lars Bak: TypeScript, JavaScript, and Dart

DartlangTV

624 subscribers • 1 video on Hallway

YouTube
  • Recommended by 4 people: 4 on Hacker News.
  • A classic. People kept recommending it from 2015 to 2022.
  • Presented by Anders Hejlsberg and Lars Bak
  • May be out of date. Uploaded 13 years ago, in an area where tools change fast.
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

14K views13 years ago4 recommendations

Programming languagesWeb developmentTypeScriptLanguage design and type systems

Anders Hejlsberg and Lars Bak debate the best approach to improving JavaScript development, comparing TypeScript's static typing with Dart's VM-based model.

Lars Bak and Anders Hejlsberg talk about Dart, TypeScript and JavaScript with Channel 9 while attending GOTO2012 in Aarhus.

Why it's here

4 people recommend this

What people say. Recommended as a classic debate between the creators of TypeScript and Dart on their differing approaches to scaling JavaScript development.

okareamanon Hacker News • Recommends

On “Interview with Anders Hejlsberg on Delphi (1995)”

Another really great video is Anders and Lars Bak around the time Typescript and Dart came out (about the same time.) In this video Anders explains to Lars why TypeScript will win the race to fix JavaScript's drawbacks. Lars was really happy with their Dart VM (as he should be) and didn't really want to hear how TypeScript would prevail. The thing about Anders is that he's usually right and he was. Anders Hejlsberg and Lars Bak: TypeScript, JavaScript, and Dart link to this video

brodoon Hacker News • Recommends

On “Dart's Macro Language”

When there is no Dart VM in the browser I honestly don't see any advantage over TypeScript. Two VMs inside each other (with two garbage collectors) will always be slower and use more memory than just one. Additionally, you always need to ship the runtime with all your scripts. You also have to use FFI to interact with Javascript. All the advantages over plain JS you mentioned above are also present in TypeSctipt (or not needed). There is also a nice discussion about TypeScript and Dart here: link to this video

dundariouson Hacker News • Recommends

On “Flutter is the most popular cross-platform mobile SDK”

This is really some armchair psychoanalysis on my part, totally not worth anything in the way of intellectual attention, but I always found this interview with both Typescript and Dart leads to be interesting. link to this video I can't help but infer that Lars is quite often a little bit frustrated with the emergence of Typescript. But on top of it being embarrassing for me to imagine up such personal rivalries based on hardly anything, you could view the interview as Dart-hostile given the interviewer.

mwattsunon Hacker News • Recommends

On “Flutter is better than React Native in all the ways that don’t matter”

If you're curious, this is an informative video of a debate between the designer of TypeScript and the designer of the Dart VM about which was the better approach. Anders Hejlsberg and Lars Bak: TypeScript, JavaScript, and Dart link to this video

ceronmanon Hacker News • Mentions

On “AtScript Primer”

I really like the idea of static type checking, but I'm not convinced about the usefulness of runtime checking. It will introduce a performance penalty and it will go against duck typing, which is one of the coolest features of languages like JS. It seems that this project is trying to build something in between of TypeScript and Dart: they want the optional runtime type checking of Dart vs the good interoperability with JS of TypeScript. In this interview 1 Anders Hejlsberg and Lars Bak (from TypeScript and Dart) discuss the idea of runtime type checking. They don't seem very convinced of the idea either. 1 link to this video

michaelwwwon Hacker News • Mentions

On “Why We Need WebAssembly: An Interview with Brendan Eich”

…o from Google predicting Dart would replace JavaScript [link ]. It created an atmosphere of hostility towards Dart that I'm sure the developers didn't deserve. I now understand your objections and I'm sorry I lumped you in with the general hostility. My own doubts about Dart after using it for a commercial app, began after watching this video [video ] where Anders Hejlsberg and Lars Bak discuss Dart and TypeScript. I felt Anders made a better case for TypeScript and Lars was feeling a bit threatened, which confirmed for me that Anders was right. Considering where Dart and TypeScript are today, I made the right choice moving to TypeScript. The other problem that I felt wasn't being addr…

michaelwwwon Hacker News • Mentions

On “Why I'm joining the Dart Team”

> trying to justify why something is still relevant or important in a company roadmap While I know what you mean, I didn't read the article that way at all. The author isn't a marketing type or someone high up in the company, but a programmer making a calculation about Dart and passing on his observation to his friends, who don't see that situation the way he does. Dart has received a lot of bad press because some Dart engineers made the mistake of saying it would replace JavaScript. I didn't get involved in defending JavaScript from Dart and wrote a bunch of Dart, and I noticed I was about twice as productive. I also learned along the way that Google was heavily invested in something called…

michaelwwwon Hacker News • Mentions

On “Ten Years of TypeScript”

Debate (almost 10 years ago) TypeScript vs. Dart about the best way to improve JavaScript Anders Hejlsberg (Microsoft) and Lars Bak (Google): TypeScript, JavaScript, and Dart link to this video

ignoramouson Hacker News • Mentions

On “Node.js adds experimental support for TypeScript”

> There was no real competition There was: Anders Hejlsberg and Lars Bak: TypeScript, JavaScript, and Dart link to this video (2013). Summary: link / link