CultRepo
Software evolution has stalled because the tech industry patches over flawed legacy systems with feature bloat instead of transitioning to clean languages and operating systems, Crockford argues.
AI-assisted summary of Why We Should Stop Using JavaScript According to Douglas Crockford (Inventor of JSON) — original source. Check the original for full context.
Source published:
Key ideas
- Douglas Crockford, creator of JSON and early JavaScript champion, has completely reversed his position, calling JavaScript a fundamentally broken and 'smelly language' with congenital defects that the industry must abandon. (0:00)
- Software language evolution has stalled: while previous generations transitioned naturally through Fortran, C, C++, Java, and JavaScript, the developer ecosystem currently refuses to adopt newly designed languages. (0:45)
- Rather than rebuilding flawed foundations across the web and operating systems, the industry compounds architectural mistakes by continuously layering features on top of broken runtimes. (1:12)
- Crockford argues that adopting clean languages, runtimes, and operating systems after a full generation of JavaScript should be seen as normal software evolution rather than a radical stance. (1:45)
Detailed notes
## Background Published on YouTube by CultRepo on June 1, 2023, this video features Douglas Crockford, the creator of JSON and longtime JavaScript advocate. The description highlights Crockford's provocative reversal on JavaScript, calling it a 'smelly language' and exploring why he believes the developer community needs to finally retire it.
## TL;DR Douglas Crockford reflects on his transition from a leading JavaScript champion two decades ago to arguing for its complete abandonment today due to inherent design defects. He points out that the software industry used to transition naturally through language generations—such as Fortran, C, C++, Java, and JavaScript—but has now stalled because developers refuse to adopt new languages. Crockford extends this critique to modern operating systems and the web, arguing that developers compound architectural flaws by piling on features rather than deploying clean, minimal runtimes. Ultimately, he insists that replacing JavaScript after a generation of use should be embraced as ordinary technological evolution rather than treated as a radical opinion.
## Atmosphere & style The clip carries an unvarnished, world-weary candor, feeling like a sobering reality check delivered by an elder statesman of the tech industry. Crockford speaks with calm, matter-of-fact bluntness, displaying zero sentimentality toward the technology that defined his career. His delivery strips away industry hype, making what could sound like a shocking attack on web development feel like a sensible, pragmatic plea for cleaner engineering.
## Bulletin - [00:00](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=0s) Douglas Crockford, creator of JSON and early JavaScript champion, has completely reversed his position, calling JavaScript a fundamentally broken and 'smelly language' with congenital defects that the industry must abandon. - [00:45](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=45s) Software language evolution has stalled: while previous generations transitioned naturally through Fortran, C, C++, Java, and JavaScript, the developer ecosystem currently refuses to adopt newly designed languages. - [01:12](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=72s) Rather than rebuilding flawed foundations across the web and operating systems, the industry compounds architectural mistakes by continuously layering features on top of broken runtimes. - [01:45](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=105s) Crockford argues that adopting clean languages, runtimes, and operating systems after a full generation of JavaScript should be seen as normal software evolution rather than a radical stance.
## Key takeaways - [00:00](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=0s) Twenty years ago, Douglas Crockford championed JavaScript, arguing that it was far better than its reputation and capable of changing the world. - [00:20](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=20s) Crockford's advocacy has fully inverted, moving from teaching developers how to use JavaScript to arguing that they should retire it entirely. - [00:31](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=31s) JavaScript suffers from inherent, congenital defects at its core, making it a fundamentally 'smelly language.' - [00:40](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=40s) Even if JavaScript remains the best tool currently available for its domain, being the best by default is no longer acceptable. - [00:47](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=47s) Historically, the software industry underwent generational language shifts roughly once every few decades, moving from Fortran to C, C++, Java, and then JavaScript. - [01:00](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=60s) The generational adoption cycle has stopped; brilliant new languages are still being designed, but the broader programming community fails to adopt them. - [01:12](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=72s) The World Wide Web and contemporary operating systems were built with foundational architectural flaws that have never been corrected. - [01:25](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=85s) Industry responses to software flaws consist of endlessly piling on features, which introduces fresh complexities and bugs rather than solving root issues. - [01:33](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=93s) The technology exists to create reliable, clean minimalist operating systems, runtimes, and programming languages, but the industry lacks the will to switch. - [01:45](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=105s) Having devoted an entire generation of his career to JavaScript, Crockford believes moving on to whatever comes next is a natural evolutionary step rather than a radical position.
## Detailed walkthrough ### [00:00](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=0s) From JavaScript Evangelist to Calling It a Smelly Language
Douglas Crockford reflects on the dramatic reversal in his relationship with JavaScript over the past two decades. Twenty years ago, he was one of the language's staunchest advocates, championing the narrative that JavaScript was vastly superior to its public reputation. His central message back then was that if developers learned to use JavaScript properly, they could build remarkable things and genuinely change the world—an outcome he notes actually came to pass. However, his mission has now shifted completely in the opposite direction, as he now believes developers must abandon it altogether.
```mermaid flowchart LR accTitle: Evolution of Programming Language Generations accDescr: Douglas Crockford's progression through programming languages over successive generations leading to current stagnation. subgraph Generations["Generational Progression"] L1["Fortran"] --> L2["C"] L2 --> L3["C++"] L3 --> L4["Java"] L4 --> L5["JavaScript"] end subgraph Current["Current Era"] L5 -.->|"Stagnation / Lack of Adoption"| L6["Next Generation?"] end ```
Crockford does not mince words when diagnosing the language's flaws, describing it as fundamentally broken at its core. As Douglas Crockford bluntly summarizes his current evangelism: “That it has so many congenital defects it really is a smelly language.” While he concedes that JavaScript might still be the best tool currently available for its specific domain of application, he insists that being the best by default is simply not good enough anymore. In previous decades, the industry naturally cycled through major languages roughly once every generation—a timeline he lived through personally, transitioning from Fortran to C, C++, Java, and then JavaScript. Yet, that evolutionary cycle has ground to a halt; while individual developers continue to design exceptional new languages, the broader programming community no longer adopts them.
- Twenty years ago, Crockford advocated for JavaScript on the grounds that it was far better than people realized and capable of transforming the software landscape. - Crockford's current stance is that the industry must move on, as JavaScript is bogged down by inherent defects and an accumulation of flawed design decisions. - Historically, an industry-wide generational shift occurred every few decades across major languages (Fortran → C → C++ → Java → JavaScript), but modern adoption for newly created languages has effectively stalled.
[01:12](https://www.youtube.com/watch?v=lc5Np9OqDHU&t=72s) Software Stagnation and the Evolutionary Case for Clean Systems
Broadening his critique beyond just JavaScript, Crockford targets the wider software landscape, arguing that both the World Wide Web and modern operating systems are riddled with foundational mistakes. Rather than fixing these architectural flaws or replacing legacy platforms, the tech industry remains trapped with defective infrastructure. The standard response across the industry has become compounding the problem by continually heaping new features onto existing systems, which inevitably introduces an endless stream of fresh bugs and complexities.
Crockford laments that computing does not have to remain in this state of perpetual feature bloat. The industry possesses the capability to build and deploy clean, minimalist operating systems paired with clean programming languages and clean runtimes, which would yield far more reliable software architectures. Instead, developers and organizations seem entirely unwilling to make that leap. Having dedicated a full generation of his career to JavaScript, Crockford believes it is high time to usher in whatever comes next, maintaining that wanting to move forward should be the default expectation rather than an outlier opinion. As Douglas Crockford insists: “And I don't think that should be a considered a radical point of view; I think it should be a normal evolutionary view.”
- Legacy mistakes in the web and operating systems are continuously patched over by piling on new features rather than rebuilding clean foundations. - Adding features to fundamentally flawed architectures consistently generates new complications and failure modes. - Crockford advocates for an ecosystem built around clean operating systems, clean runtimes, and clean programming languages to achieve genuine reliability. - Moving past JavaScript after a full generation should be treated as a standard step in software evolution rather than a controversial or radical stance.
## Mentioned Douglas Crockford, JavaScript, JSON, Fortran, C, C++, Java, World Wide Web
## Video description "JavaScript is a smelly language"! Hey, don’t hate the messenger, it’s Douglas Crockford, the cheeky creator of JSON and (former?) JavaScript evangelist who says so! Even though Douglas has spent decades working on JavaScript, he now believes it’s high time we all stopped using it. Do you want to know why? Watch this video and let us know what you think in the comments below.
Check out the home for untold developer stories around open source, careers and all the other cool stuff developers are doing at cult.honeypot.io.
Honeypot is a developer-focused job platform, on a mission to get developers great jobs. Wanna see what we're all about? Visit honeypot.io to find a job you love.
To learn more about Honeypot: https://bit.ly/3LpAkcU
Follow Douglas: Website and blog: https://www.crockford.com Github: https://github.com/douglascrockford
Follow us: Twitter: https://twitter.com/honeypotio LinkedIn: https://www.linkedin.com/company/honeypotio/ Instagram: https://www.instagram.com/honeypot.cult/
[Source](https://www.youtube.com/watch?v=lc5Np9OqDHU)