From JavaScript to ES6 - how ChakraCore changes the game
summary
Claims that ChakraCore is now a standalone, open‑source JS runtime with a three‑tier JIT, lower memory use and faster Node.js runs than V8 in their benchmarks; shows time‑travel debugging integrated into Visual Studio/VS Code and working on async code; warns that widespread use of Babel hides ES6 from engines so browsers don’t get optimized; demos ChakraCore on Raspberry Pi 2 and reports real gains in startup and memory for embedded/IoT scenarios.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:05The Old Issues
- 6:50Type Safety
- 18:13Dependency Hell
- 22:10Debugging Frameworks
- 22:31Server Side Image Optimization
- 27:51Es6
- 32:52Syntax Errors
- 35:42Standards and Interop
- 40:06Breaking Monopolies
- 42:40Microsoft Edge
- 44:33Time Travel Debugging
- 46:30Typescript Compilation
related talks
32mMaking ES6 happen with ChakraCore and Node
32mThe Story of Node-Chakracore
31mInside Chakra
32mWhat does Chakra do with your JavaScript?
37mChakra - Building A New JavaScript Engine For Internet Explorer 9
41mVirtual Machines 101
21mJavaScript MOJO with chakra
28mThe Past, Present and Future of JavaScript Engines