Brian Kernighan on JavaScript and Software Dependencies

A 2020 conversation about language evolution and package complexity.

BKBrian KernighanGuest
Channel
Lex Fridman
Published
Jul 20, 2020
Video
3:40
Read
1 min
Original
English
Open on YouTube
Scroll to read and the video shrinks to the bottom-right corner. Captions follow your reading language.
Reading languageAvailable in 2 languages
You're reading the original English.
SUMMARY

In 30 seconds

Kernighan discusses JavaScript’s improvements and the security and debugging challenges of large dependency trees.

  1. 1EvolutionKernighan notes improvements in language and tooling.
  2. 2UncertaintyHe avoids predicting total dominance.
  3. 3DependenciesLarge dependency trees can be hard to inspect.

Takeaways

  1. JavaScript and its tooling have evolved.
  2. Libraries make development more complex.
  3. Dependencies introduce security and robustness questions.
FULL TEXT

Read the edited text by chapter

Transcript only
01

JavaScript’s evolution

Lex Fridman asks Brian Kernighan about JavaScript’s growth despite its early reputation as an irregular language.

Lex Fridman asks Brian Kernighan about JavaScript’s growth despite its early reputation as an irregular language.

Kernighan says both the language and compilation technology have improved, making it viable for front-end and back-end work.

He says he has written some JavaScript but does not consider himself an expert; he expects it to remain important without predicting it will dominate everything.

02

Libraries and dependencies

Fridman asks about modern programming’s reliance on libraries built by other people.

Fridman asks about modern programming’s reliance on libraries built by other people.

Kernighan contrasts earlier work with today’s large dependency trees, which can be difficult to understand or debug.

He raises security and robustness concerns when developers install many packages without knowing their contents. These are his concerns about dependency management.

More from this channel

3 slides3:34:27EN
Lex Fridman· Oct 26, 2026Podcast · 4 speakersAI, Mathematics, and the Meaning of a ProofGuest Steven Brunton, Ankur Moitra, Alex Kontorovich · Host Lex FridmanLex Fridman and three mathematicians discuss recent AI-generated research, hard open problems and what human understanding contributes.MathematicsAI for scienceAI research+2
3:36:56EN
Lex Fridman· Sep 16, 2026PodcastPsychiatry Has Never Found Its PenicillinHost Lex FridmanHistorian Andrew Scull tells Lex Fridman why the field can ease symptoms, has never cured a major mental illness, and keeps paying for overconfidence with patients' lives.Mental HealthPublic HealthNeuroscience
5:15:51EN
Lex Fridman· Aug 26, 2026Podcast · 2 speakersDHH Did Not Write a Line of Omarchy QuattroGuest DHH · Host Lex FridmanThirteen months after a skeptical conversation with Lex Fridman, the Rails creator describes how Opus 4.5, a swarm of coding agents, and a one-minute Linux installer ended his era of hand-chiseled Ruby.Coding agentsVibe CodingAgent engineering+3
3:12:58EN
Lex Fridman· Aug 12, 2026Podcast · 2 speakersOne Cold Shower, Twenty Champions: How Khabib Nurmagomedov Was ForgedGuest Khabib Nurmagomedov · Host Lex FridmanIn a Makhachkala school gym, seventy men shared one shower, and the water was only cold.Martial ArtsCombat SportsCoaching+3
3:46:18EN
Lex Fridman· Jul 28, 2026Podcast · 2 speakersIf You Take Slavery Out of the Picture, There Is No Civil WarGuest Gary Gallagher · Host Lex FridmanIn 1860, enslaved people were worth more than every railroad and factory in the United States combined.Political PhilosophyLeadershipHistory
3:51:47EN
Lex Fridman· Jun 30, 2026Podcast · 2 speakersForty-Six Percent of Emperors Were Overthrown. The Empire Lasted AnywayGuest Anthony Kaldellis · Host Lex FridmanHistorian Anthony Kaldellis walks Lex Fridman through 2,200 years of Roman history and argues that what we call Byzantium was Rome itself.Political PhilosophyGeopoliticsLeadership