Comments by "Charles M." (@charlesm.2604) on "The Biggest Change In React’s History" video.

@seasonsunite Render HTML which ships JavaScript that modify the DOM. It's still HTML.
4
It won't replace Laravel, it won't replace your back-end (API, database communications, mailers, etc..). The only difference is that your front-end is now really generated on the server-side the same way PHP does it.
2
@BleedingDev Almost like the stale-while-revalidate cache invalidation strategy never existed. Imagine if Vercel had released a library called useSWR back in 2019 to solve this exact issue, life would have been so different... 🤦‍♂
1
You do realize when a React component makes an API call client-side, the API is doing of all those DB calls ? If they're done server or client, it doesn't matter.
1
@SeanJMay I wasn't talking about user experience but about the performance aspect. Those DB calls still need to be made and wether they're made during server side rendering or upon an API request doesn't change the fact that they still happen. As for caching, server side caching exist for a reason, and it's even more effective as the data will be cached for every request, no matter if the client already cached it or not (e.g: new visitors).
1
@SeanJMay That's not what I'm arguing about brother, care to read a reply ?
1
@SeanJMay Your original comment discussed how performances would be impacted as far as DB calls go and opposed traditional server side rendering vs. client calling API. I'm not arguing against you, if the client loads static data directly and shows a skeleton for dynamic data, uses hydration, doesn't re-download client cached content, etc... It makes for a better user experience. I'm not saying it's not the case. I'm saying the DB calls are still performed.
1
@SeanJMay Aight boss I'm not reading all that clearly you're very immature for your age if you refuse to understand you misread a reply. Have a good one now stop spamming my notification feed.
1