Yeah right! "Democracy in Andhra Pradesh is alive and thriving" @naralokesh 👏🏼👏🏼
Here's a live example. While YSRCP MPTC candidates were submitting their nomination papers for Local Body Elections to the election officer, TDP leader entered the election officer's room, snatches nomination forms from the hands of the returning officer and discards them.
x.com/Telugufeedsite…
A record of over 22,800 nominations have been filed for the urban local body elections across Andhra Pradesh. Candidates from every party, every community and every corner of the state have stepped forward. Democracy in Andhra Pradesh is alive and thriving.
Those who cry foul
All these people in replies saying next is full stacky framework it’s never bro what it mean full stack ?
these is what rubbish thing any engineer can feed himself like . i never heard from next.js core team member calling next as a full stacky framework never
even they didn’t marketed it as full stack framework at all people assume it’s just because it brought some niceties
reason behind the name convention from middleware.ts -> proxy.ts happened for this illusions coming from engineers they treated it like Express.JS middleware a place where you can drop in arbitrary logic, database calls, or complex authorization stacks things are so different in next js middleware so they called it as Proxy core team is forcing you to acknowledge its actual purpose lightweight network gateway that sits in front of your app to handle redirects, rewrites, and header manipulation
rsc’s are not ssr with extra steps , client components are also rendered i n server .why turbopack is slow in dev mode there is reason for eveything they don’t want to ship bloat itself
it’s engineered in the way
and see next don’t work same as Laravel , spring boot or any kinda backend framework it’s frontend lean thing
hmm . in this age understanding the things exact what they are is the real +
next is not any abstractions all i see it just it abstracts the network boundary you can still track everything how it works haha so it depends on you .
this people even abstracts the basic concepts and call next is bloated talk about cve every meta framework I know had even insane cve then what react had now people just forget things
In Cowork, you give Claude access to a folder on your computer. Claude can then read, edit, or create files in that folder.
Try it to create a spreadsheet from a pile of screenshots, or produce a first draft from scattered notes.
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 @tan_stack start and @nextjs and daily I use it but comparing them superficially is nonsense here I want to talk on both sides of the coin around both the frameworks
let me make a hardcore and naked rant around this firstly people compare it with
Bundle size. People always start here. Stop. That is surface-level nonsense. TanStack Start gzipped is smaller, 100–120 kB. Next.js bigger, 150–176 kB. Smaller doesn’t automatically mean faster.
If your SSR isn’t optimized, your tiny bundle doesn’t help at all. Next.js ships more JS because it runs the RSC runtime, streaming, and hydration logic. That’s intentional, not bloat.
Comparing bundles here is like comparing a bicycle to a freight truck. One is small, one actually carries the load.
smaller bundle size in start ≠faster first paint if SSR isn’t optimized.
export default function Page() {
return (
<>
// server-only
// server-only
// client-only, hydrated
>
)
}
Partial hydration in Next.js means only the interactive parts ship JS. Tiny bundle doesn’t automatically equal speed. Real users care about time to interact, not gzip stats.
SSR and hydration. TanStack Start gives explicit SSR control per route. You know exactly what runs where. Dev experience is predictable, clean.
Next.js uses RSC and hybrid SSR. Only client parts that need interactivity hydrate. Smaller payload, faster TTI, but async boundaries and Suspense can be confusing. Debugging can feel like your stack traces just vanished. Community benchmarks show TanStack Start : FCP/TTI at 1100/1600 ms, Next.js RSC at : 1050/1200 ms. So Next.js can feel faster in real apps even if the bundle is bigger.
Type safety and server functions. TanStack Start is sexy here. You get end-to-end type safety for routes, loaders, server functions. Next.js requires manual validation and can cause runtime errors.
export const getTodos = createServerFn({ method: 'GET' })
.inputValidator(zodValidator(z.object({ userId: z.string() })))
.handler(async ({ data }) => db.todos.findMany({ where: { userId: data.userId } }));
const todos = await getTodos({ data: { userId: '123' } });
That is predictable. Next.js doesn’t do this automatically yet.
Developer experience. TanStack Start has a lightning-fast Vite dev server, instant HMR, explicit SSR. Predictable local dev makes coding joyful.
Next.js uses Turbopack or Webpack. HMR is slower, heavier dev tooling, but it comes with powerful production defaults: automatic image optimization, caching, SEO, ISR.
Reality: TanStack Start equals dev-first happiness, Next.js equals production-first performance. Both valid, hype-driven debates are useless.
Caching and data fetching. TanStack Start gives explicit caching per route. You can fine-tune everything, but one misconfiguration and you’re chasing ghosts. Next.js has built-in caching through ISR and streaming. Less manual work, but you need to understand it or you get surprising bugs.
Hydration and streaming complexity. TanStack Start is explicit, predictable, clean. Easy to debug. Next.js streams server components, uses Suspense, smaller interactive payloads, faster TTI, but debugging is harder. Async boundaries will bite you if you don’t fully understand streaming logic.
Production vs dev tradeoffs. TanStack Start is lightweight, dev-first, predictable, makes you happy while coding. Next.js is production-first, bigger bundle, hybrid SSR complexity, optimized for user experience.
Stop judging these frameworks by hype tweets or gzip numbers. Look at SSR control, hydration, developer experience, caching, type safety, and real production performance. That’s the real comparison.
people who hate @nextjs first learn fundamentals. if you wanna go deep , rsc, isr, edge, hydration i made a dedicated repo:
github.com/renderhq/raw-b…
devs cry about next.js all day. hydration bug, isr loop, streaming broken, lcp slow. 99% it’s their own lack of understanding toward the web lol
they don’t get what is runtime, break file-based routing, misuse rsc hooks, fail edge constraints, double-fetch waterfalls, hydration mismatches, slow lcp, suspense deadlocks or whatever this repo shows how it really works . understand fundamentals → master runtime → app router → rsc → isr → edge → hydration
this may feel some what harder . but dm me we can change it fast fast the way it would really great im curious to see all opinion cus im not only the smart next js ever lol
2K Followers 2K Following#टीम_महापंचायत 25 yrs building technology. Sharing insights on practical AI, photography, travel & Chennai. Author.
Read my deep-dives at my website 👇
2K Followers 2K Following#टीम_महापंचायत 25 yrs building technology. Sharing insights on practical AI, photography, travel & Chennai. Author.
Read my deep-dives at my website 👇
194K Followers 8 FollowingMakers of Devin, the first AI software engineer. We are an applied AI lab building end-to-end software agents. Join us: https://t.co/4Ss9hvpjRG
504K Followers 0 FollowingSentenced to die in prison. Pardoned by President Trump after spending 4,130 days (11+ years) in max security. Freedom is sweet!