3 ms·

Here are some simplifications that are worth mentioning, I think, of course, it's easy to find fault with any of them. But I'd be curious in what you think is a

Here are some simplifications that are worth mentioning, I think, of course, it's easy to find fault with any of them. But I'd be curious in what you think is a better alternative. - loader, action, component colocation - code splitting without thinking about it - automatic data revalidation on mutation - useFetcher for optimistic updates In terms of the fancier things (the react components) -- none of that is necessary. Personally, I don't use <Await> or <Defer> at all. Although it's nice to know that I need to pull some performance levers, I have those options. One React component that I do use a lot is <Link>. The thing I love about it is that I can add a <Link prefetch="intent"> to it, and I'll get an near-instant page load when I click it. The web APIs that I work with in Remix are Request, Response, Headers, Cookie and FormData.

troupo 3y ago
> Here are some simplifications that are worth mentioning, I think, of course, it's easy to find fault with any of them. But I'd be curious in what you think is a better alternative. Simplification compared to what? A better alternative to what? > In terms of the fancier things (the react components) -- none of that is necessary. It doesn't matter if they are necessary or not, they are there in the framework. > The web APIs that I work with in Remix are Request, Response, Headers, Cookie and FormData. That's.... it? You call that "leans heavily into Web APIs"? Have you ever thought of what backend services do all day everyday? These are not "web apis". These are wrappers over HTTP.