10 Things I Regret About Node.js

on YouTube ↗27m

" summary

Names specific regrets: promises removed causes async/await momentum loss, Node gives full system access so there is no sandbox security, and the C build chain depends on jip build system while package.json plus vendored-by-default node_modules resolution creates needless complexity. A one‑month‑old prototype called deno bundles TypeScript into a single executable, starts at ~1s today (plans for V8 snapshots), uses Parcel for bundling, and deliberately drops Node compatibility.

AI-written summary · about

" chapters (13)

1. 0:00Introduction
2. 3:28Dynamic languages role
3. 5:03Regret over Promises removal
4. 6:14Security oversight
5. 7:23JIP build failure
6. 10:08Package JSON complexity
7. 13:17Node modules drawbacks
8. 15:33Module system afterthought
9. 17:11Deno secure runtime
10. 19:54TypeScript modern features
11. 21:05Module imports simplification
12. 23:22Single executable future
13. 25:11Uncaught errors browser

" related talks

• 39mThe Structure of Node.JS ApplicationsTim Oxley · JSConf.Asia 2015
• 33mPanel: The State of Node.jsMichael Dawson, Mikeal Rogers, Tracy Hinds, Trevor Livingston, Dave Ings · Cloud Foundry Summit Silicon Valley 2017
• 02h 24mHow to Node.js - Part 2Matteo Collina · OpenJS World 2022
• 27mState of Node.js SecurityVladimir de Turckheim · NodeConf NL 2019
• 29mMyles Borins - KeynoteMyles Borins · Nordic.js 2017
• 46mState of Node.js 2025: While You Were Building Frontend...Igor Antonov · HolyJS 2025 Autumn
• 25mThe Alleged 'End' of Node.js is Much Ado About NothingMatteo Collina · Devworld Conference 2025
• 53mDeno – a better Node.js?Krzysztof Piechowicz · International JavaScript Conference Munich 2019