What Dillon Mulroy thinks about TypeScript
Principal engineer at Cloudflare as of 2026, on agents and developer tooling. Streams TypeScript, OCaml and Neovim on Twitch, and wrote the better-result library after writing the same Result type about a hundred times.
Dillon Mulroy did not write this page.
We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.
Filter TypeScript · Newest first
Only Dillon Mulroy on TypeScript. See everyone on TypeScript
4 dated positions, 2023 to 2026, in their own words. Our reading of what Dillon Mulroy has said — not written or endorsed by them.
-
Their wordsevery time i’ve built something without effect over the past almost 3 years ive come to deeply regret it and wish i had just done it from the start
- 8 months earlier
-
Their wordsintroducing better-result, my opinionated take on the rust result type for typescript after having written about 100 times npm i better-result *disclaimer*: if you can use effect-ts, you should use effect-ts
- 13 months earlier
-
Their wordsthe most important typescript feature is discriminated unions and everyone should be using them more
- 13 months earlier
-
Their wordsOne thing that drives me crazy about the React ecosystem, and more specifically "tech influencers" and "thought leaders" in the space, is the infantilization of the developers using and working in it. I’m tired of reading takes like TypeScript generics, mapped types, etc should only be needed and used by library authors for most use cases. Or today’s discourse; Don’t use `useCallback’, ‘useMemo’, and React.memo. If you’re building anything beyond a simple CRUD app or a an incredibly focused app with few features, you _will_ need these features.