Calling a new URL triggers the execution of 20,000 lines of C++ code each time, leading to a significant performance impact. Running a Node index without files creates new URLs five times and a fetch operation generates five new ones. Importing modules in ESM also adds to the complexity. These seemingly small actions have a cumulative effect on performance, known as the '1000 cuts' phenomenon. The extensive code raises questions about its purpose and necessity in handling URLs, attributed to a group named WEG, the web application bubble.
Yagiz Nizipli talks about his involvement with Node.js, implementing .env, how he finds areas to improve in performance, the happy path vs the hot path, and new features coming to Node.js.
Show Notes
- 00:32 Welcome
- 01:01 Introducing Yagiz Nizipli
- 02:21 What is your involvement in Node.js?
- 03:27 Implementing .env
- 07:03 Why was 20,000 lines of C required?
- 11:00 How do you begin to find performance issues?
- 15:17 How do you measure improvements?
- 26:27 The happy path vs the hot path
- 27:36 Is Rspack ready for prime time?
- RSpack
- 28:47 Bundle Size VS runtime perf? Whats more important?
- 30:51 What’s it like working on a large project like Node?
- 38:26 Will Node ever get TypeScript support?
- 40:22 What are loaders?
- 44:24 Node.js is getting a config file?
- 51:37 Sick Picks
Sick Picks
Shameless Plugs
Hit us up on Socials!
Syntax: X Instagram Tiktok LinkedIn Threads
Wes: X Instagram Tiktok LinkedIn Threads
Scott:X Instagram Tiktok LinkedIn Threads