Hacker News: tannerlinsley

New comment by tannerlinsley in "TanStack Start Now Support React Server Components"

tannerlinsley — Tue, 14 Apr 2026 14:26:15 +0000

You’re the only one

New comment by tannerlinsley in "TanStack Start Now Support React Server Components"

tannerlinsley — Tue, 14 Apr 2026 07:21:29 +0000

It works, but once again, you will be left without a stable native caching mechanism in React unless you put the stream into state. Use Query, or Router, or something.

New comment by tannerlinsley in "TanStack Start Now Support React Server Components"

tannerlinsley — Tue, 14 Apr 2026 07:19:53 +0000

Thanks guys!

New comment by tannerlinsley in "TanStack Start Now Support React Server Components"

tannerlinsley — Tue, 14 Apr 2026 07:19:27 +0000

Correct. People need to stop conflating SSR with RSC. Well said.

New comment by tannerlinsley in "TanStack Start Now Support React Server Components"

tannerlinsley — Tue, 14 Apr 2026 06:03:51 +0000

Coming soon!

New comment by tannerlinsley in "TanStack Start Now Support React Server Components"

tannerlinsley — Tue, 14 Apr 2026 06:03:41 +0000

Thank you!

New comment by tannerlinsley in "React is winning by default and slowing innovation"

tannerlinsley — Tue, 16 Sep 2025 02:02:45 +0000

Thank you for your kind words and support!

Next.js vs. TanStack

tannerlinsley — Tue, 18 Mar 2025 20:25:02 +0000

Article URL: https://www.kylegill.com/essays/next-vs-tanstack/

Comments URL: https://news.ycombinator.com/item?id=43404609

Points: 13

# Comments: 4

TanStack Form V1 – Type-Safe, Agnostic, Headless Form Library

tannerlinsley — Mon, 03 Mar 2025 16:49:40 +0000

Article URL: https://twitter.com/tannerlinsley/status/1896595066778743136

Comments URL: https://news.ycombinator.com/item?id=43243694

Points: 10

# Comments: 0

Why React Query?

tannerlinsley — Wed, 08 May 2024 20:45:53 +0000

Article URL: https://ui.dev/why-react-query

Comments URL: https://news.ycombinator.com/item?id=40302567

Points: 9

# Comments: 2

New comment by tannerlinsley in "TanStack Router v1"

tannerlinsley — Sun, 24 Dec 2023 21:04:35 +0000

Announcement: https://x.com/tannerlinsley/status/1738709130213560497?s=46&...

TanStack Router v1

tannerlinsley — Sun, 24 Dec 2023 21:04:33 +0000

Article URL: https://tanstack.com/router/v1

Comments URL: https://news.ycombinator.com/item?id=38756851

Points: 8

# Comments: 1

New comment by tannerlinsley in "[dead]"

tannerlinsley — Mon, 26 Jun 2023 15:59:45 +0000

Keyword clustering that finds the overlapping URLs in the top 10 between SERPs to generate clusters with actionable metrics like Traffic Opportunity, Max Estimated Traffic, and more. You can start improving your content and SEO based on real data.

New comment by tannerlinsley in "Observable Plot: A JavaScript library for exploratory data visualization"

tannerlinsley — Fri, 28 Apr 2023 20:44:49 +0000

You have no idea how excited I am about this.

New comment by tannerlinsley in "TypeScript is terrible for library developers"

tannerlinsley — Tue, 23 Aug 2022 20:45:49 +0000

TLDR: I write and maintain several good-sized typescript libraries so I write library types all the time. In fact, I'm writing them right now! TypeScript is what makes them really fun to use. They infer everything they can and have very high levels of safety and passthrough while still allowing for composition and extension at the framework-adapter and library level. I will never consider writing another OSS tool in the JS ecosystem without ensuring the typescript experience is the best I can offer.

That said...

I've learned that "library" types might not be the best way to talk about these concepts. What we're really talking about here are types that are complex/advanced enough to force you to venture beyond the primitive building blocs in the TS docs and into existing open source solutions that have trail-blazed more advanced use-cases. It took me only a few weeks to get comfortable with common TS, but at least a year to feel dangerous enough to write more advanced TS. I'm on year 3 now and I am still learning/forgetting so much about it.

I agree that: - Advanced types and their concepts are difficult to learn. - There is limited documentation on how to create/use them. - They can sometimes be difficult to reason about, mainly due to the limited syntax TS offers around advanced concepts.

On the the positive: - They can be learned with practice. - There is plenty of OSS out there to learn from - Once you learn them, you start to think differently about TS as a language instead of annotations

I wish there were better features/syntax support for: - Optional generics - Higher-order generics / Polymorphic generics (basically higher-order functions, but for types) - More built-ins (like ts-toolbelt, type-fest, etc)

I think this ramp of difficulty with advanced TS types is fine for the most part. Library authors have always carried way more of a burden than devs at the edge, even during runtime to ensure things like size, performance, flexibility, etc. TS is just another facet that is becoming more an expectation every day.

At the end of the day, a library dev gets to choose what level of investment they'll put into great types for their library. If they can pull it off, their tool will likely provide a measurably better developer experience.

That's my goal for my libraries, so choosing to go all-in on advanced TS is now a no-brainer.

Anywho, good luck!