Alright we’re going to lightly touch on this and if there’s enough of a public outcry, we’ll gladly do a deep dive but for now let’s skim over client side Vs. server side rendering. YAY!!<\/p>\n
Now, full disclosure: It’s better to watch the video than to spend time reading what’s being written. The video is quick articulate and makes good and knowledgeable arguments for sides better than writing this out. But if you still feel like reading on, here’s the (very<\/em>) skinny…<\/p>\n CLIENT SIDE RENDERING: So when you’re looking at the app\/website, the views you render\/send out (to the web browser) for the client to see. Generally you want to keep the views pretty simple when it comes to the processing power behind it. SERVER SIDE: Does not rely on your viewers having the most up to date web-browser or fastest computer but it does require a lot of server side processing power…<\/p>\n So what’s a dev to do?<\/p>\n Check out our video for answers and opinions.\u00a0 Enjoy!<\/p>\n
\nThe downside? Not everyone has the same hardware on their computers and may encounter trouble viewing the page (ex: web browsers not up to date, lag, slow load times, etc.)<\/p>\n