“Any application that can be written in JavaScript, will eventually be written in JavaScript.”
Jeff Atwood offered this line in his Coding Horror essay “All Programming is Web Programming”. Atwood coined the line while arguing that the browser had become an unusually efficient distribution network for software. He acknowledged that recreating desktop applications in JavaScript could look technically irrational while predicting that reach and immediacy would keep pulling software toward the web. The source makes clear that the remark grew from experience, not from a prediction made at a distance.
Deployment constraints can outweigh language preference. A runtime already available to users, connected to a global network, and updated through a URL has an adoption advantage that can compensate for performance or tooling compromises. Put into practice, the idea changes what a team measures and which tradeoffs it is willing to defend. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
The sentence is deliberately provocative, not a rule that JavaScript is best for every task. Native software, servers, embedded systems, and specialized computing retain strong reasons to use other languages and distribution models. A careful application therefore asks where the analogy stops as well as where it illuminates. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Web technologies now power editors, creative tools, collaboration suites, and cross-platform shells. Atwood’s prediction reminds architects that distribution is part of product design: the easiest software to reach may outperform a technically purer system users cannot conveniently obtain. Applied carefully, the idea helps teams turn historical insight into choices that can be tested and revised. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Jeff Atwood offered this line in his Coding Horror essay “All Programming is Web Programming”. Atwood coined the line while arguing that the browser had become an unusually efficient distribution network for software. He acknowledged that recreating desktop applications in JavaScript could look technically irrational while predicting that reach and immediacy would keep pulling software toward the web. The source makes clear that the remark grew from experience, not from a prediction made at a distance.
The source record connects the wording to his Coding Horror essay “All Programming is Web Programming”, which is the context used for this post.
Deployment constraints can outweigh language preference. A runtime already available to users, connected to a global network, and updated through a URL has an adoption advantage that can compensate for performance or tooling compromises. Put into practice, the idea changes what a team measures and which tradeoffs it is willing to defend. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
The interpretation focuses on a decision or design principle that readers can test against actual systems.
The sentence is deliberately provocative, not a rule that JavaScript is best for every task. Native software, servers, embedded systems, and specialized computing retain strong reasons to use other languages and distribution models. A careful application therefore asks where the analogy stops as well as where it illuminates. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Web technologies now power editors, creative tools, collaboration suites, and cross-platform shells. Atwood’s prediction reminds architects that distribution is part of product design: the easiest software to reach may outperform a technically purer system users cannot conveniently obtain. Applied carefully, the idea helps teams turn historical insight into choices that can be tested and revised. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.
