remix

Thanks for the bug report. We could stand to have a better catch-all error page for this case. Looks like this browser API is used by Remix’s new Single Fetch feature, which coincidentally we just started using last week. Sorry we broke the site for you. We don’t have as clear of a browser support policy as we probably should, but if we did, I doubt we would be guaranteeing support for two year old browsers unless we had a customer request for it. https://github.com/remix-run/remix/blame/cc65962b1a96d1e1343...

The remix package is no longer used[1]. Remix's central package is @remix-run/router[2], which has 5,627,846 downloads per week. [1] https://github.com/remix-run/remix/pull/9433 [2] https://www.npmjs.com/package/@remix-run/router

> extremely hostile to anything resembling stability Remix has one of the best stars/issue ratios I've ever seen in a large project. They have 27k stars for 228 issues (118 stars/issue). Meanwhile next.js has 121k stars for 2678 issues (45 stars/issue). Remix also has a robust future flag system to ensure nothing breaks during transitions. https://github.com/remix-run/remix/issues/4598 For larger changes (like the controversial flat routes), they even maintain the old feature so you don't have to upgrade. https://www.npmjs.com/package/@remix-run/v1-route-convention I don't think the evidence supports your assertion.

Yes. The use of loaders and actions blurs the lines between client and server. It's really productive. There are a few gaps that need filling, one that comes to mind is internationalisation [1] I am very surprised that NextJS has left it so long to consider mutations - they're apparently coming up with an RFC on that but it seems to be somewhat behind closed doors. [1] https://github.com/remix-run/remix/discussions/2877

Why acquire something that is MIT licensed? Is this really just a talent acquisition? https://github.com/remix-run/remix

You want to avoid the complexity of react by using a platform that wraps react with more complexity? Remix is based on react if you didn't know: https://github.com/remix-run/remix/blob/main/package.json#L9...

Someone has brought up adding a Remix integration to Solito, too. It's certainly possible from my end, the question is if Remix would make it possible. Many remix APIs like Form seem to be very browser-specific, so it wouldn't share nicely with React Native. That said, I opened this discussion on the Remix repo a while ago: https://github.com/remix-run/remix/discussions/1578 If you're using shared screens outside of Remix marketing pages, though, then I imagine a solito/remix could exist to bring the same features the Next integration has to a Remix one.

Not according to the package.json. https://github.com/remix-run/remix/blob/main/package.json

Looks like you are correct, I don't know where I got the idea that Remix does partial hydration from: https://github.com/remix-run/remix/discussions/680

They just did a demo with a simple form and looking at it seemed so obvious. There was no useState per form element, form data was trivially validated on the server, errors were trivially sent down to the server. If you look at this example[0] you'll see there's not a single useState, useEffect, etc. Fundamentally, Remix is about using native browser behavior to build websites. The imported `Form` component is replaceable with the HTML `form` element and it all still works. I think Remix is going to be even better than NextJS. This isn't a rivalry though, just an alternative solution. Clearly NextJS and React frameworks broadly are valuable, Remix is now another option. I really like that Remix's architecture means you end up writing code that would execute on your server and not the client. It feels like a much nicer balance rather than

Some context: - Remix creators are the authors of React Router (v6 was released recently: https://reactrouter.com/) - Remix was initially a closed source paid framework then moved to open source. - They raised a $3M seed funding in October: https://remix.run/blog/seed-funding-for-remix - Kent C. Dodds, a very prolific React developer, joined them as a Co-Founder and Director of Developer Experience Also see: - https://github.com/remix-run/remix - https://remix.run/ - https://kentcdodds.com/blog/how-i-help-you-build-better-webs... - https://www.youtube.com/watch?v=wsJaUjd1rUo