News for hackers. Stuff that matters.
Re:No-build, no-NPM, SSR-first JavaScript framework if you h... by rsmtjohn on Tuesday March 24, 2026 @10:10AM (#47502877)
I have been building with Next.js for years and still reach for it by default, but I genuinely appreciate the philosophy here. The no-build approach eliminates an entire class of problems -- stale caches, bundler config drift, slow CI pipelines -- that we have collectively normalized as "just how frontend works."

The SSR-first angle is especially interesting. Most frameworks bolt on SSR as an afterthought. Starting from HTML and progressively enhancing is how the web was designed to work, and it is telling that we keep circling back to it.

Re:No-build, no-NPM, SSR-first JavaScript framework if you h... by esperent on Tuesday March 24, 2026 @10:31AM (#47503164)
I've been building out a fairly complex app. I decided to avoid Next.js some I went with a simple Hono + Tanstack Router/query. With Vite 8, my build time is about ~0.8s.

I've also go a much simpler Next.js app with a build time of 45s.

Re:No-build, no-NPM, SSR-first JavaScript framework if you h... by steve_adams_86 on Tuesday March 24, 2026 @04:33PM (#47508779)
That stack is such a breath of fresh air. And so easy to deploy anywhere.

I do love the idea of a batteries included framework for the JS ecosystem, like the mythical Rails for node, but as long as we're gluing random stuff together... This is a really nice combo. I also love using Hono and React/Vite with TRPC.

I stopped working with Next a few years ago, so I can't comment very fairly on recent changes in the framework. However, it does appear as though it has become even more complex, and that was a significant art of what steered me away. The other part was simply a lack of cohesion with design decisions and direction. The middleware layer seemed like a poor design. Various opinions around things like default cache policies felt incorrect. I found myself battling their decisions too often, for too little benefit.