Related posts
Dave Rupert GitHub
ts-errors — Look up any TypeScript error: humanized explanations + side-by-side broken/fixed examples with real squiggles.
The subject this post names, from the same vocabulary the directory files beliefs under, and the words it uses that this site has seen least often elsewhere. Posts are matched on those words alone — nothing here is a summary of this one.
Top people
Showing Profile →
Hiding
Hiding
20 September
17 September
16 September
15 September
12 September
11 September
10 September
9 September
8 September
7 September
1 September
-
korrents.com
If you can use Effect for TypeScript, you should -- to the point of not starting a new project without it.Their words, before
introducing 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
Their words now
every 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
-
korrents.com
If you can use Effect for TypeScript, you should -- to the point of not starting a new project without it.Their words
every 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
24 August
23 August
20 July
17 July
10 July
20 May
From one piece Why Rust is different, with Alice Ryhl 2 beliefs, in the piece's order there
-
korrents.com
For a TypeScript team, Rust belongs on the backend — API servers — and not in the front end.Their words
But okay, so to begin with, I think when it comes to TypeScript, Rust fits in as the backend language. That's where I would put it. I wouldn't use it in the front end. I think it's a pretty good fit for backends, API servers.
-
Their words
My opinion is that the least mature area is front end. There have been some attempts to compile Rust to Web Assembly and then run it on the web as a front end as a replacement for TypeScript. But if I was writing a web server, I would totally use Rust for the back end and TypeScript for the front end. I would not really go the web assembly route.
13 May
From one piece TypeScript, C# and Turbo Pascal with Anders Hejlsberg 5 beliefs, in the piece's order there
-
Their words
that the language that's most suited for AI is the language that AI has seen the most of in its training set, right? And that's why you could argue AI does really well on JavaScript and TypeScript and Python because it's seen an awful lot of it
-
Their words
But but the thing is like doing programming languages, you come to realize it's a long play. I mean, if if you look back at the the stuff I worked on, it it it goes in 10-year cycles at least. And TypeScript didn't really, for example, or C# for that matter. I mean, it took it it takes 10 years to get to, you know, version one is great, but it has all sorts of issues, and then you got to do version two, and then it's not until version three that it really starts to be great.
-
Their words
The thing that makes it interesting, I think, and and unlike pretty much any other programming language is the gradual typing. This This notion that you can have types, but you don't have to have types.
+ 2 more
-
TypeScriptopen sourceJavaScript
Their words
And we we full well knew that there was absolutely zero chance that we would appeal to the JavaScript ecosystem with a proprietary programming language licensed from Microsoft. No. No one was going to come. It had to be open source. There was just no two ways about it, right?
-
Their words
So, if we're checking 99% instead of 100%, well, heck, that's better than the 0% that JavaScript checked, right? And it gives you like language features that no other languages can provide because they can't get to 100%.
18 April
10 March
-
Lovedrcmnd.app
TypeScriptTheir words
TypeScript - I can't imagine building JavaScript projects without TypeScript.
-
Likedrcmnd.app
ZodTheir words
Zod - A great schema declaration and data validation library for TypeScript.
14 January
28 December 2025
-
Likedrcmnd.app
GoTheir words
My go-to languages are TypeScript for web stuff, Go for CLIs and Swift if it needs to use macOS stuff or has UI. Go wasn’t something I gave even the slightest thought even a few months ago, but eventually I played around and found that agents are really great at writing it, and its simple type system makes linting fast.
20 December 2025
-
Lovedrcmnd.app
SvelteKitTheir words
elements, JavaScript reigns supreme. SvelteKit's efficiency and reactivity make it my framework of choice, and TypeScript's type annotations bring a welcome layer of confidence to my codebase.
6 November 2025
8 October 2025
-
Likedrcmnd.app
Visual Studio CodeTheir words
My primary code editor. Extensible, fast, and has excellent TypeScript support. The integrated terminal and Git features are fantastic.
22 September 2025
15 June 2025
18 December 2024
-
korrents.com
Discriminated unions are the most important TypeScript feature, and everyone should be using them more.Their words
the most important typescript feature is discriminated unions and everyone should be using them more
2 June 2024
6 November 2023
-
Their words
One 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.
20 July 2022
Nothing matches.
What is a korrent?
A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.
Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.
Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.
Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.