4 ms·
i agree it's up to the browsers chromium , Safari , and Firefox to do the diff. But we might need a new meta tag or change to the Fetch API to tell them this ht
by kgbcia 4y ago
i agree it's up to the browsers chromium , Safari , and Firefox to do the diff. But we might need a new meta tag or change to the Fetch API to tell them this html page should only update the elements that are different.
Remember <meta http-equiv="refresh" content="5"> .
It was discouraged because the back button broke. If you're developing a single page react app, I don't think you care about the back button.
- creakingstairs 4y ago> If you're developing a single page react app, I don't think you care about the back button. You should though. One easy way is to use react-router. e.g. going to /profile renders the Profile component. Then navigating to /dashboard renders the Dashboard component. Pressing the back button will take you to /profile. Another pet peeve of mine is people using internal react state when they should just use path or query params to make it transparent and easily sharable.
- alserio 4y agoThe primitives of fine grained reactive programming seem to me more amenable to be implemented by the browser than react-style whole world diffing
- nkrisc 4y ago> If you're developing a single page react app, I don't think you care about the back button. Your users likely do, so you should too.