People are mischaracterizing TanStack's move from RSC as "RSC is an overengineered solution to large dependencies."
That's not what the blog post says;
"For our site, the other possible RSC benefits weren’t valuable enough. Its decisive benefit was hiding our huge renderer. Once we made that renderer small, RSC’s costs outweighed its remaining benefits."
The generalization is wrong; it's like saying: "We bought a truck to move a piano, then we replaced the piano with a keyboard, so the truck was unnecessary."
Code is cheap to produce; architecture is cheap to change, but complexity is still expensive to carry. Optimize for the current use case, measure the result, and keep decisions reversible.
https://t.co/E45Sc0OwZO
These sentiments are sensationalized and come from a place of inexperience. The book that teaches you how to build software in 2026 was written in 2010, and then again in 2015, and then again in 2020.
The bros building software today just won’t read those books. And instead will bring the same energy to agentic development that they brought to their NFT scams.
@GeorgeJeffersn ah, that's nice - maybe it's just the photo, and the way the ceilings are lowered below the windows, but it has aircon, which is nice! and the floor is really nice.