3 ms·
> two separate versions of your site/app. It isn't 2010 anymore. React (just to name an example, there are many others) completely avoids this issue - you get
by 15155 12y ago
> two separate versions of your site/app.
It isn't 2010 anymore.
React (just to name an example, there are many others) completely avoids this issue - you get serverside and clientside rendering out of the box.
- magicalist 12y agoYou dropped the context of that quote. React isn't exactly a poster child of progressive enhancement.
- marrs 11y agoActually it's very well suited to it (well, in theory at least - haven't tried it yet). You can render the same html on the server as on the client, using node.js, so you can build a page on the server and then let the JS enabled client take over after the initial page load, or let the server do the work for the non-JS enabled browser.