Timeline for What are the differences between server-side and client-side programming?
Current License: CC BY-SA 3.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2018 at 15:41 | comment | added | Rafael Herscovici | @ScottStensland - That statement is very inaccurate. How would you save data to the server for example, without server side logic? Security and Permissions? Connecting to protocol based API's ? Data Validation ? | |
| Mar 16, 2016 at 19:00 | answer | added | Kosta Kontos | timeline score: 3 | |
| Jan 12, 2015 at 12:37 | answer | added | logc | timeline score: 14 | |
| S Jan 12, 2015 at 7:49 | history | suggested | Community Bot | CC BY-SA 3.0 |
fixed grammar
|
| Jan 12, 2015 at 7:14 | review | Suggested edits | |||
| S Jan 12, 2015 at 7:49 | |||||
| Nov 4, 2014 at 16:54 | comment | added | Scott Stensland | When the web was young it was good practice to put most of your logic heavy lifting on the server side (java/c++) and keep browser logic intentionally thin - particularly since browsers back then were not ready for prime time. Now this emphasis has reversed such that browser based tools (Angular.js) are where the bulk of the web application heavy lifting logic now resides (away from the increasingly stripped down server side logic). This has been facilitated by modern industrial strength browsers running extremely fast javascript engines (within an order of magnitude of native code). | |
| Sep 1, 2013 at 15:42 | history | notice added | user28988 | Needs detailed answers | |
| Sep 1, 2013 at 15:42 | history | protected | Community Bot | ||
| Aug 21, 2013 at 19:27 | history | reopened | Community Bot | ||
| Aug 20, 2013 at 15:35 | history | closed |
gnat Community Bot Kilian Foth ozz |
Duplicate of Difference between a server and a client [duplicate] | |
| Aug 19, 2013 at 23:55 | review | Close votes | |||
| Aug 20, 2013 at 15:35 | |||||
| Oct 27, 2012 at 4:18 | vote | accept | Madara's Ghost | ||
| Oct 25, 2012 at 3:01 | history | tweeted | twitter.com/#!/StackProgrammer/status/261301497680252928 | ||
| S Oct 24, 2012 at 17:50 | history | suggested | K.Steff | CC BY-SA 3.0 |
Suggestion for an edit limiting the question to web development
|
| Oct 24, 2012 at 17:42 | review | Suggested edits | |||
| S Oct 24, 2012 at 17:50 | |||||
| Oct 24, 2012 at 17:06 | comment | added | Madara's Ghost | @KSteff you are welcome to edit my question to add that. | |
| Oct 24, 2012 at 14:42 | comment | added | K.Steff | I think you should include in the question that you refer only to web programming, as in the current form the answers are not complete. For example, server-client communication need not be done in HTTP; client side might not use a browser, etc. | |
| Oct 24, 2012 at 14:36 | answer | added | Tulains Córdova | timeline score: 26 | |
| Oct 24, 2012 at 14:21 | answer | added | Madara's Ghost | timeline score: 127 | |
| Oct 24, 2012 at 14:16 | comment | added | JeffO | This one is pretty good: programmers.stackexchange.com/questions/138561/… | |
| Oct 24, 2012 at 14:13 | comment | added | FrustratedWithFormsDesigner | Server-side programming is writing code that runs on the server, using languages supported by the server (such as Java, PHP, C#; it is possible to write code that executes on the server-side in JavaScript). Client-side programming is writing code that will run on the client, and is done in languages that can be executed by the browser, such as JavaScript. | |
| Oct 24, 2012 at 14:08 | history | asked | Madara's Ghost | CC BY-SA 3.0 |