I haven't tried Remix but I can relate to Next.js being too much magic. I've had errors in `getServerSideProps` that happen on the server and then
again in the client, causing a client side error instead of simply rendering the 500 page. I've accidentally bundled server code in the client because there's no clear separation. The automagical client side navigation with <Link> has caused scroll position to be forgotten when navigating back.
I recently tried Deno Fresh and it has made many different choices that I resonate with:
- "When you create a route, all of the components used are rendered on the server. No javascript is sent to the client, unless you specifically include something from the /islands/ folder."
- "For stronger resiliency and user experience, Fresh relies on native browser support for form submissions with the HTML <form> element."
For example a route that renders a form and accepts a `POST` with that form is trivial, which amazingly can not be said for many server side React frameworks.
I recently tried Deno Fresh and it has made many different choices that I resonate with:
- "When you create a route, all of the components used are rendered on the server. No javascript is sent to the client, unless you specifically include something from the /islands/ folder."
- "For stronger resiliency and user experience, Fresh relies on native browser support for form submissions with the HTML <form> element."
For example a route that renders a form and accepts a `POST` with that form is trivial, which amazingly can not be said for many server side React frameworks.