Tap a claim on the ring to put it at the centre.
← Calling static typing the only way to build reliable systems is…
17 connected korrents · 15 moments from 15 Apr 2010 to 20 May 2026.
Everything filed under Ruby on Rails
Ruby on Rails
Everything filed under coding agents
coding agents
Everything filed under JavaScript
JavaScript
Everything filed under Ruby
Ruby
Everything filed under TypeScript
TypeScript
Everything filed under formal proof
formal proof
Everything filed under developer tools
developer tools
Everything filed under compilers
compilers Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Read this korrent: Calling static typing the only way to build reliable systems is idiotic in the face of the evidence, starting with Shopify serving a million requests a second on Rails. Calling static typing the only way to build reliable systems is idiotic in the face of the evidence, starting with Shopify serving a million requests a second on Rails. Last stated a year ago
12 Jul 2025
DH
David Heinemeier Hansson — holds since 2025-07-12 — tap for who they are
Same subject: Ruby must never get static typing: dynamic duck typing is the essence of what makes Ruby Ruby. — tap to centre the map on it Ruby must never get static typing: dynamic duck typing is the essence of what makes Ruby Ruby. Last stated a year ago
12 Jul 2025
DH
David Heinemeier Hansson — holds since 2024-09-18 — tap for who they are
DH
David Heinemeier Hansson — holds since 2025-07-12 — tap for who they are
Same subject: Layering a static type system atop a dynamic one, capable of proving the dynamic checks redundant, combines the flexibility of dynamic typing with the performance of static typing. — tap to centre the map on it Layering a static type system atop a dynamic one, capable of proving the dynamic checks redundant, combines the flexibility of dynamic typing with the performance of static typing. Last stated 6 months ago
22 Apr 2026
JB
Jamie Brandon — holds since 2026-04-22 — tap for who they are
Same subject: There is one right way to build a type system, the way that gives you mathematical proofs, and every other kind of type system is simply worse and should be rejected. — tap to centre the map on it There is one right way to build a type system, the way that gives you mathematical proofs, and every other kind of type system is simply worse and should be rejected. Last stated a year ago
30 Apr 2025
TS
Tim Sweeney — holds since 2025-04-30 — tap for who they are
Same subject: Enforcing safe mutable value semantics (e.g. via borrow-checking) is far easier to do cheaply with a static type system than with a dynamic one. — tap to centre the map on it Enforcing safe mutable value semantics (e.g. via borrow-checking) is far easier to do cheaply with a static type system than with a dynamic one. Last stated 6 months ago
22 Apr 2026
JB
Jamie Brandon — holds since 2026-04-22 — tap for who they are
Same subject: Static typing does not require manifest typing — type inference lets a language avoid that without becoming dynamically typed. — tap to centre the map on it Static typing does not require manifest typing — type inference lets a language avoid that without becoming dynamically typed. Last stated 17 years ago
15 Apr 2010
AO
Allan Odgaard — holds since 2010-04-15 — tap for who they are
Same subject: The empirical literature on static typing finds effects too small to matter, in the narrow settings it has managed to study. — tap to centre the map on it The empirical literature on static typing finds effects too small to matter, in the narrow settings it has managed to study. Last stated 12 years ago
7 Nov 2014
DL
Dan Luu — holds since 2014-11-07 — tap for who they are
Same subject: You cannot build good tooling without a type system — decent tooling perhaps, but nothing that scales to a large team. — tap to centre the map on it You cannot build good tooling without a type system — decent tooling perhaps, but nothing that scales to a large team. Last stated 5 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting. — tap to centre the map on it A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting. Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: Rails is enjoying an influx of a new generation of programmers — tap to centre the map on it Rails is enjoying an influx of a new generation of programmers Last stated a year ago
6 Sept 2025
DH
David Heinemeier Hansson — holds since 2025-09-06 — tap for who they are
Same subject: Rails is having a renaissance because it is one of the most token-efficient ways to build a web app, which suits agents, for as long as that lasts. — tap to centre the map on it Rails is having a renaissance because it is one of the most token-efficient ways to build a web app, which suits agents, for as long as that lasts. Last stated 6 months ago
8 Apr 2026
DH
David Heinemeier Hansson — holds since 2026-04-08 — tap for who they are
Same subject: Ruby on Rails took off because its creator evangelized it by arguing its superiority against the competing alternatives. — tap to centre the map on it Ruby on Rails took off because its creator evangelized it by arguing its superiority against the competing alternatives. Last stated 2 years ago
2 Jun 2024
DH
David Heinemeier Hansson — no longer holds since 2024-06-02 — tap for who they are
Same subject: The Rails doctrine's 'progress over stability' is the one point that dated: churn is not progress, and stability turned out to be worth more. — tap to centre the map on it The Rails doctrine's 'progress over stability' is the one point that dated: churn is not progress, and stability turned out to be worth more. Last stated a year ago
12 Jul 2025
DH
David Heinemeier Hansson — no longer holds since 2025-07-12 — tap for who they are
Same subject: 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. — tap to centre the map on it 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. Last stated 7 months ago
2 Apr 2026
MS
Marvin Schwaibold — holds since 2026-04-02 — tap for who they are
Same subject: A proprietary language licensed from Microsoft had zero chance in the JavaScript ecosystem: TypeScript had to be open source or nobody would come. — tap to centre the map on it A proprietary language licensed from Microsoft had zero chance in the JavaScript ecosystem: TypeScript had to be open source or nobody would come. Last stated 5 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: "I don't know" becomes a kind of superpower when you can work with Claude Code to figure things out. — tap to centre the map on it "I don't know" becomes a kind of superpower when you can work with Claude Code to figure things out. Last stated 7 months ago
19 Mar 2026
KP
Kris Puckett — holds since 2026-03-19 — tap for who they are
Same subject: A coding agent does not learn from its mistakes the way a person does -- it repeats the same error indefinitely unless a human notices and writes it down. — tap to centre the map on it A coding agent does not learn from its mistakes the way a person does -- it repeats the same error indefinitely unless a human notices and writes it down. Last stated 7 months ago
25 Mar 2026
MZ
Mario Zechner — holds since 2026-03-25 — tap for who they are
Same subject: A coding agent left to run over a weekend returns work that is half good, a quarter garbage and a quarter in need of repair. — tap to centre the map on it A coding agent left to run over a weekend returns work that is half good, a quarter garbage and a quarter in need of repair. Last stated a year ago
18 Aug 2025
CB
Clay Bavor — holds since 2025-08-18 — tap for who they are
At the centre
Calling static typing the only way to build reliable systems is idiotic in the face of the evidence, starting with Shopify serving a million requests a second on Rails.
Holds Read this korrent →
Ruby must never get static typing: dynamic duck typing is the essence of what makes Ruby Ruby.
Holds
Layering a static type system atop a dynamic one, capable of proving the dynamic checks redundant, combines the flexibility of dynamic typing with the performance of static typing.
Holds
There is one right way to build a type system, the way that gives you mathematical proofs, and every other kind of type system is simply worse and should be rejected.
Holds
Enforcing safe mutable value semantics (e.g. via borrow-checking) is far easier to do cheaply with a static type system than with a dynamic one.
Holds
Static typing does not require manifest typing — type inference lets a language avoid that without becoming dynamically typed.
Holds
The empirical literature on static typing finds effects too small to matter, in the narrow settings it has managed to study.
Holds
You cannot build good tooling without a type system — decent tooling perhaps, but nothing that scales to a large team.
Holds
A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting.
Holds
Rails is enjoying an influx of a new generation of programmers
Holds
Rails is having a renaissance because it is one of the most token-efficient ways to build a web app, which suits agents, for as long as that lasts.
Holds
Ruby on Rails took off because its creator evangelized it by arguing its superiority against the competing alternatives.
No longer holds
The Rails doctrine's 'progress over stability' is the one point that dated: churn is not progress, and stability turned out to be worth more.
No longer holds
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.
Holds
A proprietary language licensed from Microsoft had zero chance in the JavaScript ecosystem: TypeScript had to be open source or nobody would come.
Holds
"I don't know" becomes a kind of superpower when you can work with Claude Code to figure things out.
Holds
A coding agent does not learn from its mistakes the way a person does -- it repeats the same error indefinitely unless a human notices and writes it down.
Holds
A coding agent left to run over a weekend returns work that is half good, a quarter garbage and a quarter in need of repair.
Holds