No-build JavaScript works in production and caches better: one bundle turns over every time a semicolon changes, while small separate files live forever.

Added to korrents 5 Sept 2026 · How quotes work · Something wrong? Tell us

Where this collides

• Cannot both be true

  The complexity of a JavaScript bundling and transpiling toolchain is a bargain worth making, and the right default for building web applications.

  Hansson made both cases and has turned on the first: that a bundling and transpiling toolchain is a bargain worth making, and that no-build JavaScript works in production and caches better because small files live forever while a bundle turns over on every semicolon. The claims still exclude each other, and the record of him abandoning the first is the point.

Shared subject first, then similar wording. They may agree or disagree.

• A designer's assumption about where a component belongs is a personal assumption and does not mean that the market or the users will react to the component that way. MSMarvin Schwaibold2 Apr 2026JavaScript
• A proprietary language licensed from Microsoft had zero chance in the JavaScript ecosystem: TypeScript had to be open source or nobody would come. AHAnders Hejlsberg13 May 2026JavaScript
• Because its types are erased before the program runs, TypeScript can afford not to be sound: checking 99% beats the 0% JavaScript checked, and buys features a sound language cannot offer. AHAnders Hejlsberg13 May 2026JavaScript
• Fiscal multipliers vary across time and place but are generally nonzero, positive for spending, negative for taxes, and larger when monetary policy cannot offset them. OBOlivier Blanchard1 Jun 2022JavaScript
• Front-end is, at the end of the day, CSS and JavaScript, and Claude (Opus in particular) and Composer are really great at it. AMAndy Madrick26 May 2026JavaScript

On the map

Open the map on its own page