logoalt Hacker News

esperent04/23/20253 repliesview on HN

> I personally don't like that direction so looking forward to exploring new frameworks

I personally am becoming dissolutioned with React because of this, as a former strong advocate.

Next.js and Remix - or whatever the hell it's called this week - are both over-engineered messes.

Yes, I'm aware that I don't have to use them, but they are where the momentum and energy of the community is being spent in recent years. And I do want a monolithic framework, I just want one that focuses on simplicity and ease of development rather than one designed to funnel me into using Vercel.


Replies

n8cpdx04/23/2025

Don't worry, we're only four or five years out from the react community discovering/inventing a totally fresh UI paradigm where the entire app is run on the client, no server rendering at all.

It will be totally fresh and solve all the annoying problems of legacy react server pages. Of course then 6 months later they'll discover a need to make it work with SEO...

show 1 reply
qudat04/23/2025

Hard agree. It’s all complexity and for what? SEO? So many products don’t need SEO. API proxies with secrets? These are not super common use cases.

The default should be SPA and purely static.

brulard04/24/2025

next.js totally is overengineered and feature-bloated. But working with remix in the last 3 years (now called React Router: framework mode) I would never label it as overengineered. I'm not sure what you are talking about. If anything, it still misses features (Middleware still in beta, websockets native support, etc.). This weeks flavor is TanStack Start - which looks quite promising and not yet overengineered as well.