Hacker News Reader

> Routing, state management, auth, components, theming, API access, and more are all still problems that people add libraries for

A lot of this goes away if you choose a server-side framework that handles its own routing, auth, api, templates etc. And the state management also goes away if you don't need complex stateful widgets on the frontend.

View on HN

> And the state management also goes away if you don't need complex stateful widgets on the frontend.

Browsers come with a very limited selection of widgets, almost everything I make requires at least one custom widget, usually significantly more than one. How can you possibly know when you start a project that you won't need to make any complex stateful widgets?

If they really are that complex, then use react for them. One of the biggest issues I have always had with react proponents is the "well if I need react for X then I might as well build the whole thing in react."

Islands Architecture is really not complicated. The bulk of your app can be very simple hypermedia exchanges and components and when you need a really fancy widget, load it and mount it where it needs to be.

You can build a complex stateful widget in a MPA.

Reply on news.ycombinator.com