x.com/i/article/2009…

Server Actions are lying a lot by omission They make network calls look like local code. That’s fine until something breaks badly . Then you realize you don’t know where the boundary is, because the boundary was intentionally hidden by the framework I don’t like

the core reason server actions feels weird for me there are mostly implicit in nature . I won’t make a rant on any features based on there capability tbh i make rants around there implicitness it’s has implicit serialization , http , cache side effects, auth context let me

10 days into 2026: - Terence Tao announces GPT & Aristotle solve Erdős problem autonomously - Linus Torvalds concedes vibe coding is better than hand-coding for his non-kernel project - DHH walks back “AI can’t code” from Lex podcast 6 months later An acceleration is coming the

the thing i love is at runtime in cache components suspense is not for just loading ui it’s clean pre render boundary layered

🐻 Zustand v5.0.10 is out! Fixes an edge case in the persist middleware. github.com/pmndrs/zustand… Thanks as always for the support. This is such a nice community.

Notice how in the correct example chips move instantly to their new position when a chip is removed. That’s because of the `popLayout` mode on AnimatePresence in motion/react which creates a smoother, faster transition when removing an element.

o boy we made this 4 months ago Kimino so Anthropic is our real competition we are team of 3 btw

oh well , Kimino can do it too :D

billion dollar company vs our cto ayana

we called it Claude code for rest of us see the diff join waitlist Kimino gonna be in 1 week for sure early bird get the worm of the workflow ?

React.memo looks like performance work, but most of the time it’s just extra bookkeeping. You’re not removing work, you’re adding a check. Every time a parent renders, React first shallow-compares the previous props with the next ones. That comparison itself costs time, usually

I literally laugh when I see people comparing TanStack Start and Next.js like one is automatically better. Most devs follow hype, most humans follow hype disclaimer : I love both TANSTACK start and Next.js and daily I use it but comparing them superficially is nonsense here

Isaac Hinman Jean P.D. Meijer ― 🇪🇺 eu/acc Next.js downloads grew 2x in the last year and still accelerating: x.com/timneutkens/st… More than 2016 till 2024 combined. There's clear usage (and growth) across every category of application and every type of company. Don't believe everything you see on X. You can see an

I've officially been Claude Code pilled after making this last night

We're encapsulating all our knowledge of React & Next.js frontend optimization into a set of reusable skills for agents. This is a 10+ years of experience from the likes of Shu, distilled for the benefit of every Ralph

Theo - t3.gg hype bros in X re inventing the PHP lol ? 🤣 there is no concept of server driven ui in php as Next.js . These guys can’t tell diff between templating and ui orchestration . The real irony : this php guys would love if it existed then . Let me tell if php has component

render 100%. React.memo is usually a bandaid that just hides underlying architectural issues. my self-imposed guidelines: - avoid function props that aren’t event handlers. stick to data down, actions up - prefer primitive props (handlers the exception). use compound parts so i’m not