Videos / Web Dev

Episode 5 of 16 · Web development, end to end

Node versus the browser: same language, different machine

Chapters

1. An engine on a bench0:00
2. What the engine provides0:16
3. Notice what is missing0:35
4. Two global objects0:53
5. The middle they share1:11
6. Two very different lives1:28
7. A guest in a stranger's house1:46
8. The page as a tree2:03
9. One thread, sixteen ms2:21
10. The request that comes back2:38
11. Storage, in layers2:55
12. The walls3:13
13. The keys to the building3:31
14. First, the disk3:47
15. Second, the process4:04
16. Third, the socket4:22
17. Fourth, the whole machine4:40
18. The uncomfortable part4:58
19. Two plugs, one wall5:16
20. CommonJS runs while it loads5:35
21. ES modules resolve first5:52
22. What the restriction buys6:12
23. How Node picks a mode6:31
24. Interop, in one direction6:51
25. One clerk, one back room7:11
26. The loop's phases7:27
27. Waiting that costs nothing7:46
28. Files need real threads8:03
29. The thing that blocks8:20
30. Another thread, both sides8:38
31. A room that boots when you knock8:56
32. Isolates, not processes9:13
33. What the edge takes away9:30
34. What it gives back9:49
35. The baseline everyone shares10:07
36. Keep the host at the edge10:26
37. The whole thing10:43

Node versus the browser: same language, different machine. An engine on a workshop bench does nothing. No wheels, no fuel line, no steering. V eight is that engine. It runs the language and nothing more. Everything you actually use, a butt

Mark as watchedSaved in this browser only.