Client-side v. Server-side Rendering

By | June 2, 2017

Here's the problem with facebook and pages like it:

When you are surfing on the Internet web pages render themselves in two locations: on the originating server, or on your computer. On large systems with many subscribers, server-side rendering is minimized by using JavaScript to render their pages. JavaScript (JScript or JS) is a client-side programming language. Which means the server sends programming code to your computer that will in turn program the browser (Internet Explorer, Chrome, Firefox) to display the page in a certain way.

If you have an older system, then the JavaScript code doesn't always execute correctly due to resource limitations. (sometimes this happens in newer systems too, due to programming errors).

Facebook is constantly under development and their programmers don't always get things right. When they fumble the code, on a newer machine, the system can recover faster and you'll notice a glitch, but it recovers in a blink of an eye. In a system with less resources, the machine doesn't always recover quickly. So, you see the page fragmented.