This, plus when it comes to web dev courses, it’s mostly about wiring up 15 frameworks and libraries that were just in that week.
Deep understanding is rare to see. Seeing someone teaching it is even rarer.
Deep understanding is rare to see. Seeing someone teaching it is even rarer.
Project-based courses are the root of tutorial hell. "Follow what I type" doesn't lead to understanding.
You need an actual education. Deep conceptual understanding accompanied by coding yourself.
You need an actual education. Deep conceptual understanding accompanied by coding yourself.
December 19, 2025 at 6:35 PM
This, plus when it comes to web dev courses, it’s mostly about wiring up 15 frameworks and libraries that were just in that week.
Deep understanding is rare to see. Seeing someone teaching it is even rarer.
Deep understanding is rare to see. Seeing someone teaching it is even rarer.
A really good episode with @tannerlinsley.com
Calling the RSCs “serializable components” or “serializable virtual DOM” was particularly eye-opening.
Looking forward to trying TanStack Start — seems almost too good to be true.
topenddevs.com/podcasts/jav...
Calling the RSCs “serializable components” or “serializable virtual DOM” was particularly eye-opening.
Looking forward to trying TanStack Start — seems almost too good to be true.
topenddevs.com/podcasts/jav...
TanStack: A Deep Dive into Server Functions and Routing with Tanner Linsley - JsJ 667 - JavaScript Jabber -
-
Top End Devs
topenddevs.com
February 12, 2025 at 4:47 PM
A really good episode with @tannerlinsley.com
Calling the RSCs “serializable components” or “serializable virtual DOM” was particularly eye-opening.
Looking forward to trying TanStack Start — seems almost too good to be true.
topenddevs.com/podcasts/jav...
Calling the RSCs “serializable components” or “serializable virtual DOM” was particularly eye-opening.
Looking forward to trying TanStack Start — seems almost too good to be true.
topenddevs.com/podcasts/jav...
Tailwind v4 looks great, but it’s currently a step back from v3 in one particular area — config-first design systems.
There’s no `resolveConfig` in v4, and with CSS based configuration, there’s no easy way to pass tokens between CSS & JS.
github.com/tailwindlabs...
There’s no `resolveConfig` in v4, and with CSS based configuration, there’s no easy way to pass tokens between CSS & JS.
github.com/tailwindlabs...
Is there a plan for `resolveConfig` in Tailwind 4? · tailwindlabs tailwindcss · Discussion #14764
With Tailwind 4's CSS-first configuration approach, I would assume that this means the ability to reference values in JavaScript using the built-in resolveConfig function will no longer be possible...
github.com
February 12, 2025 at 4:39 PM
Tailwind v4 looks great, but it’s currently a step back from v3 in one particular area — config-first design systems.
There’s no `resolveConfig` in v4, and with CSS based configuration, there’s no easy way to pass tokens between CSS & JS.
github.com/tailwindlabs...
There’s no `resolveConfig` in v4, and with CSS based configuration, there’s no easy way to pass tokens between CSS & JS.
github.com/tailwindlabs...