Tap a claim on the ring to put it at the centre.
← Application code should contain no unsafe at all: unsafe is how you…
17 connected korrents · 12 moments from 12 Dec 2015 to 4 Oct 2026.
Everything filed under design
design
Everything filed under taste
taste
Everything filed under simplicity
simplicity
Everything filed under cybersecurity
cybersecurity
Everything filed under coding agents
coding agents
Everything filed under TypeScript
TypeScript 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: Application code should contain no unsafe at all: unsafe is how you add a missing feature to the language, not how you write a server. Application code should contain no unsafe at all: unsafe is how you add a missing feature to the language, not how you write a server. Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: The guarantee Rust makes is conditional: write no unsafe, and no amount of bad code can produce a memory-safety bug. — tap to centre the map on it The guarantee Rust makes is conditional: write no unsafe, and no amount of bad code can produce a memory-safety bug. Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: The unsafe keyword does not switch the borrow checker off; it only unlocks a few operations you then have to justify yourself. — tap to centre the map on it The unsafe keyword does not switch the borrow checker off; it only unlocks a few operations you then have to justify yourself. Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: Writing to files safely is too hard to do with raw syscalls; application code should go through a library or a database. — tap to centre the map on it Writing to files safely is too hard to do with raw syscalls; application code should go through a library or a database. Last stated 11 years ago
12 Dec 2015
DL
Dan Luu — holds since 2015-12-12 — tap for who they are
Same subject: Safety guardrails make a coding model more dangerous rather than less, because one refusal turns it into something that refuses anything. — tap to centre the map on it Safety guardrails make a coding model more dangerous rather than less, because one refusal turns it into something that refuses anything. Last stated 2 months ago
31 Aug 2026
PL
Pieter Levels — holds since 2026-08-31 — tap for who they are
Same subject: For a TypeScript team, Rust belongs on the backend — API servers — and not in the front end. — tap to centre the map on it For a TypeScript team, Rust belongs on the backend — API servers — and not in the front end. Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: Memory safety means an entire class of bug is impossible no matter how bad the code is — and it is the class that becomes security vulnerabilities. — tap to centre the map on it Memory safety means an entire class of bug is impossible no matter how bad the code is — and it is the class that becomes security vulnerabilities. Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: What trips up newcomers to Rust is not the code but the shape of their data. — tap to centre the map on it What trips up newcomers to Rust is not the code but the shape of their data. Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: The case for Rust is stronger against C++ than against JavaScript, because in C++ an ordinary mistake is usually a security vulnerability. — tap to centre the map on it The case for Rust is stronger against C++ than against JavaScript, because in C++ an ordinary mistake is usually a security vulnerability. Last stated 5 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: A $1,299, 100-gram pair of slip-on glasses seems far more enticing than a $3,699, 700-gram headset strapped to the face. — tap to centre the map on it A $1,299, 100-gram pair of slip-on glasses seems far more enticing than a $3,699, 700-gram headset strapped to the face. Last stated 4 weeks ago
24 Sept 2026
MS
M.G. Siegler — holds since 2026-09-24 — tap for who they are
Same subject: A baby-step version of eval-driven design is to sketch out 10 to 20 hero flows and run the feature or interaction through them to see where it falls apart. — tap to centre the map on it A baby-step version of eval-driven design is to sketch out 10 to 20 hero flows and run the feature or interaction through them to see where it falls apart. Last stated a month ago
9 Sept 2026
EB
Ed Bayes — holds since 2026-09-09 — tap for who they are
Same subject: A blank chat box is lazy: it violates the first rule of a good user experience, that it is obvious what you can do. — tap to centre the map on it A blank chat box is lazy: it violates the first rule of a good user experience, that it is obvious what you can do. Last stated a year ago
12 May 2025
JZ
Julie Zhuo — holds since 2025-05-12 — tap for who they are
Same subject: A browser works better as a single window than as multiple separate windows. — tap to centre the map on it A browser works better as a single window than as multiple separate windows. Last stated a month ago
15 Sept 2026
CC
Chris Coyier — holds since 2026-09-15 — tap for who they are
Same subject: A business is more likely to fail from taking on too much complexity than from lacking resources. — tap to centre the map on it A business is more likely to fail from taking on too much complexity than from lacking resources. Last stated 8 years ago
29 Sept 2018
TG
Tren Griffin — holds since 2018-09-29 — tap for who they are
Same subject: A business succeeds through a small number of highly effective distribution channels, not many mediocre ones. — tap to centre the map on it A business succeeds through a small number of highly effective distribution channels, not many mediocre ones. Last stated 3 years ago
17 Feb 2024
AW
Adam Wiggins — holds since 2024-02-17 — tap for who they are
Same subject: A big part of taste is delivering high levels of craft in an accessible way so that as many people as possible can experience it. — tap to centre the map on it A big part of taste is delivering high levels of craft in an accessible way so that as many people as possible can experience it. Last stated 6 months ago
21 Apr 2026
BJ
Brandon Jacoby — holds since 2026-04-21 — tap for who they are
Same subject: A company name can have different appeal to corporate buyers versus their customers. — tap to centre the map on it A company name can have different appeal to corporate buyers versus their customers. Last stated 3 weeks ago
4 Oct 2026
PG
Paul Graham — holds since 2026-10-04 — tap for who they are
Same subject: A first draft should not be graded good or bad; it is only the material that taste then gets to act on. — tap to centre the map on it A first draft should not be graded good or bad; it is only the material that taste then gets to act on. Last stated 3 months ago
6 Aug 2026
GS
George Saunders — holds since 2026-08-06 — tap for who they are
At the centre
Application code should contain no unsafe at all: unsafe is how you add a missing feature to the language, not how you write a server.
Holds Read this korrent →
The guarantee Rust makes is conditional: write no unsafe, and no amount of bad code can produce a memory-safety bug.
Holds
The unsafe keyword does not switch the borrow checker off; it only unlocks a few operations you then have to justify yourself.
Holds
Writing to files safely is too hard to do with raw syscalls; application code should go through a library or a database.
Holds
Safety guardrails make a coding model more dangerous rather than less, because one refusal turns it into something that refuses anything.
Holds
For a TypeScript team, Rust belongs on the backend — API servers — and not in the front end.
Holds
Memory safety means an entire class of bug is impossible no matter how bad the code is — and it is the class that becomes security vulnerabilities.
Holds
What trips up newcomers to Rust is not the code but the shape of their data.
Holds
The case for Rust is stronger against C++ than against JavaScript, because in C++ an ordinary mistake is usually a security vulnerability.
Holds
A $1,299, 100-gram pair of slip-on glasses seems far more enticing than a $3,699, 700-gram headset strapped to the face.
Holds
A baby-step version of eval-driven design is to sketch out 10 to 20 hero flows and run the feature or interaction through them to see where it falls apart.
Holds
A blank chat box is lazy: it violates the first rule of a good user experience, that it is obvious what you can do.
Holds
A browser works better as a single window than as multiple separate windows.
Holds
A business is more likely to fail from taking on too much complexity than from lacking resources.
Holds
A business succeeds through a small number of highly effective distribution channels, not many mediocre ones.
Holds
A big part of taste is delivering high levels of craft in an accessible way so that as many people as possible can experience it.
Holds
A company name can have different appeal to corporate buyers versus their customers.
Holds
A first draft should not be graded good or bad; it is only the material that taste then gets to act on.
Holds