Hacker News

points by ogou 4 days ago | 0 comments

The vast majority of websites don't need Next.js or React. Those are only useful if you need dynamic and modular updates within the structure, or state management. We've defaulted to React because of the name recognition and simple intertia. It's not a good framework for websites in general.

[–] tempay 4 days ago

I'm not convinced you need React/Next.js even in those cases. Web components work and LLMs are so capable of using them that I find there is increasingly little utility in big frameworks.

[–] agos 4 days ago

Any web components solution is probably going to be as big as React

[–] CharlieDigital 4 days ago

Difference is in the eventing model and complexity of state management in React's hooks based model vs vanilla's. WC is aligned with how JS callbacks naturally work. React is the only framework that points the callback to the component function.

[–] EricFrost 3 days ago

I wrote Solarite b/c I wanted a simple and fast web component solution without a compilation step.

https://eric-frost.github.io/solarite/

[–] kalcode 3 days ago

These days you can write in say React or SolidJs or JSX I guess to say, and have it transformed into HTML only with no JavaScript.

You get the best of both worlds, better language than XML/HTML and yah, you can deliver only HTML since the consumer typically doesn't need all that JavaScript, spa stuff. The Island Architecture.

Feels like a good in-between. Good DX for me, great UX and mostly HTML with some JavaScript sprinkled and fallback for users.

[–] fergie 4 days ago

No idea why this idea is being downvoted, because it is totally correct, even more so in the LLM-coding era.