So first, there is an assumption that I haven't read up on React. False. By that merit you sound like a dickbag. But its cool, not judging.
Second, the point I'm making is the subsequent page loads still get data from..............the server. So while yes, the page loads are fast, there is still a request to the server. Unless we're loading all subsequent page data in state? Which seems like overkill.
And if that is the basis of an argument for React. Server (and page) caching on subsequent visits is also - fast.
Using React just to use it is totally fine. Using it assuming its "what you're supposed to do" is terrible. Using a JS framework meant for state, etc for an entirely, otherwise, static website seems overkill. Over-engineering.
But as I mentioned, if the other of the post wants to try React. A portfolio is a great use case.
So first, there is an assumption that I haven't read up on React. False. By that merit you sound like a dickbag. But its cool, not judging.
Second, the point I'm making is the subsequent page loads still get data from..............the server. So while yes, the page loads are fast, there is still a request to the server. Unless we're loading all subsequent page data in state? Which seems like overkill.
And if that is the basis of an argument for React. Server (and page) caching on subsequent visits is also - fast.
Using React just to use it is totally fine. Using it assuming its "what you're supposed to do" is terrible. Using a JS framework meant for state, etc for an entirely, otherwise, static website seems overkill. Over-engineering.
But as I mentioned, if the other of the post wants to try React. A portfolio is a great use case.