ECMAScript or TypeScript, That Is the Question
summary
Compares the latest ECMAScript (JavaScript) language features with TypeScript, naming which yearly ECMAScript additions since 2015 have narrowed gaps between the two. Discusses remaining differences — notably lack of built-in typing, inconsistent engine implementations, and JavaScript’s tolerance of syntactic issues — and evaluates whether TypeScript is still needed long-term.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:25JavaScript’s reputation
- 6:23JavaScript history
- 9:53JavaScript 2015 milestone
- 13:24Function vs block scope
- 15:33JavaScript classes
- 17:21TypeScript intro
- 20:13TypeScript vs JavaScript 2015
- 21:39TypeScript code completion
- 23:47TypeScript error detection
- 26:17Polyfills for older browsers
- 27:00TypeScript in frameworks
- 27:40TypeScript intersection types
- 28:45TypeScript for JS devs
- 30:09TypeScript null-safety
- 30:51TypeScript typing example
- 32:18Union Types typing
- 33:23TypeScript advantages
- 34:28TypeScript disadvantages
- 36:15Conclusion: TypeScript or JavaScript
- 38:25Q&A
related talks
40mJavaScript: The Standard's Evolution When Nobody Cares
47mECMAScript: latest and upcoming features
47mECMAScript 6, A Better JavaScript for the Ambient Web Era
26mECMAScript 6 is so 2015! Meet ES2016
58mES2017 vs Typescript vs Dart: Comparing Without Emotion
20mTypeScript and ES6
06mWhat’s new in ECMAScript?
01h 08mECMAScript 6: A Better JavaScript for the Ambient Computing Era