Iβm excited to join @frontendnation! π₯
Join me and thousands of frontend devs in learning through workshops, talks, and community.
Itβs online and completely FREE! π
Stay in the loop
https://t.co/kY6gOiOkr0
#frontendnation#FEN2026
I dug deeper and discovered that the culprit is likely React Compiler. Disabling it in development gave me a "significant" speed boost
https://t.co/FMJv8Sivh0
Can somebody confirm Iβm reading this right? They shipped RSC to mass-degrade React DX. And somehow also made Next.js runtime embarrassingly slower than everything else on the market. What is the point? Genuinely curious.
BTW I went through all the TanStack docs and mapped it onto my app. Havenβt migrated yet, but so far, I see literally zero reasons to pick Next for anything unless itβs a static landing page.
GitHub Issues and PRs doesn't stop at "collaborative" projects. I found out recently that adopting them for solo projects saves a lot of time, and most importantly, they define focus.
Combined with commit lint + Husky, everything just feels safe.
@alex35mil The DX dropped massively as of late, with slow rendering, and sometimes compilation, but it remains blazingly fast in production.
This is my observation as I'm currently working on a Next project rn.
1. Immediate cache to @redis upon creation, short-lived.
2. When they become global "hit," save to @vercel's Edge Config, long-lived. β
Summary:
Provide speed for all fresh data, but only "hot" data ever hits Edge for continued speed.
Purge via Cron if ever stale afterwards.
I found myself in a situation where I needed fast access to a every frequently accessed data (which might become stale later on, but might also become "hot" in a later time).
I needed to maintain speed for the hot data all the time.
My solution:ππΏ
When building a project, every step on the way is a learning & unlearning process...
A glimpse on how I structured my token refresh endpoint to implement minimal security in the case of stolen refresh token.
Yeah, I could've just used Supabase's auth system, but how'd I learn?
@dev_olayinka Late second year... Everything started stringing together after I got my first gig (a few features and fixes). The confidence boost was mad.
@an_shvert@Deepaktvit@tan_stack You have a valid point here, but over the years, Tanstack as an ecosystem has excelled really well in this game.
So IMO, we're up for a tough rivalry in the near years, and it's a good thing.
Currently, I build in Nextjs btw.
Vercel will be officially sponsoring https://t.co/QF7eOed81b. That's a given. We as a community and industry owe @adamwathan and team a lot. Tailwind is foundational web infrastructure at this point (it fixed CSS π). I've also reached out to Adam to explore how we can make this a longer-term commitment.