SSR stands for Server Side Rendering. CSR stands for Client Side rendering.  These are the two primary modes in which website content is created for your consumption. They are totally different systems, but they can be mixed together as a hybrid as well. 

This website was built to expose various travesties that have transpired in the global IT industry over the past 30 years that have left massive global populations surrounded by technology, but totally unable to truly engage with it in a satifying and equitable manner. 

This website was also built to introduce you to a newer platform that will allow us to "show you" SSR and CSR side by side, so you can personally see WHY 30% or more of Sales Force staff may have been complaining of mental health issues around COVID time. The  two may  

The internet is a highly engineered system. But, to put it bluntly, the "engineers" who know how it works and how to select platforms and solutions based on application needs have been over run by propaganda the likes most can not imagine. 

If you were told to use a spoon to cut your steak and your knife to eat your spaghetti from someone with a sraight face, you might laugh, while telling them to go jump in a lake.  

Yet, this is the exact type of advice individuals, small businesses, corporations and governments needing webservices are being given without their own knowledge --  and the only people laughing are those making the money on the inversion work. 

Summarily the internet as you know it was built for Server Side Rendering.  This is what that looks like. 

In 1995, "javasript" was created to make a monkey dance in browser.  It was just a tiny program that could be included with the html when it was sesnt to the broswer that the client could run by clicking on something.  It seems to ahve been created just for something fun to do. Then a few relevant things were bulit using javasript , like more dynamic menu systems.  And then it was discovered that javascript could be used to make calls to the server , get data back and update "parts of a screen" without erasing the rest of the screen.  This action has been labelled as "ajax" or making an "ajax call". While that is an interesting thing and might have had some merit for limited use back then, someting then went very wrong with the entire IT industry.  "They" all threw the baby out with the bathwater in the mid 2000's and nobody has asked "them" to correct the record since. 

It's unclear right now exactly who "they" are and how "they" did it and if "they" are still involved in the unconscionably confusing and profitable web development industry now -- or if those that threw it off track are long gone and it's just been mass phsychosis and lockstep since long before COVID elevated that -- but no matter, its time to correct the record so others can enjoy  what those who came along in the 1990's took for granted.  AI suggests this was part of the story..

Cargo-Cult Engineering. In the mid-2000s, Google (with Gmail/Maps) and Facebook needed SPAs because they were building highly complex, real-time desktop applications inside the browser. The "travesty" wasn't necessarily a shadow cabal; it was that millions of regular developers looked at Facebook and said, "If they are doing it, we must have to do it too." The consulting industry then happily monetized this unnecessary complexity, selling small businesses $100,000 React SPAs when a $5,000 SSR PHP/ASP site would have been faster, safer, and cheaper. Grounding the "propaganda" in this historical reality makes your argument bulletproof. 

Welcome to "Internet 2.0".  

Contrary to those with no clue what's going on, we don't need new languages and we don't really need new platforms.  What we need is engineers to explain when and how to use the various platforms available for use , and the addition of one small webserving application that has been conspicously abesent for 20 years, and is finally on the rise now to fill the GAPING HOLE that has been sitting in plain view for over 20 years. 

Welcome to "Internet 2.0".