Earlier quoted context omitted.
It’s not a value prop, it’s just a statement of remembering to use the right tools. You even mention this yourself, just not explicitly, when you say “react app” and “vanilla site”. They serve different purposes and I’ve worked with many people who do not understand because react is all they know. Remix is an improvement over react as a framework though because you can fall back on native browser functionality where…
> remembering to use the right tools 100% agree here. But if I were going to rewrite a whole application, I'd need a really good value prop. > high latency, slow devices, no JavaScript I don't see why high latency would be improved by remix, you're still fetching everything it's just without the waterfall. I've yet to see a modern-ish device (going back to iPhone 7s) that struggle so hard with rendering that progress…
It's exactly because of the waterfall. If I have to make 3 roundtrip fetches, and the latency of each is increased by 150ms, then eliminating 2 subsequent fetches will save me 300ms.
> I've yet to see a modern-ish device (going back to iPhone 7s) that struggle so hard with rendering that progressive enhancement is valuable.
I have used an uncountable number of websites that are extremely janky, slow to load, and overall unpleasant to use on mobile while traveling on trains and busses between cell towers. Some of that can be attributed to ads but the reality is you don't need SPA's to serve news. Remix is cool in that it lets you develop like an app but serve like a website.