Timeline for What are the differences between server-side and client-side programming?
Current License: CC BY-SA 4.0
24 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 20, 2018 at 19:17 | comment | added | itmuckel | An addition to clientside programming: Next to JavaScript there is WebAssembly now which is supported by all major browsers. It allows writing client side code in C++, Rust, C#... | |
| Aug 7, 2018 at 18:54 | history | edited | Dan Jones | CC BY-SA 4.0 |
Changed wording from "Displays pages" to "Compiles pages", as the client, not the server, is responsible for displaying the page.
|
| Jul 19, 2018 at 11:02 | review | Suggested edits | |||
| Jul 24, 2018 at 10:05 | |||||
| Mar 4, 2018 at 23:53 | review | Suggested edits | |||
| Mar 5, 2018 at 9:08 | |||||
| Aug 18, 2016 at 7:41 | history | made wiki | Post Made Community Wiki by Madara's Ghost | ||
| Aug 18, 2016 at 6:47 | comment | added | Julix | @MadaraUchiha - Not everyone has editing priviledges (to make those changes in your post) - and still many prefer pointing out the change and letting you implement it, so the style is consistent. | |
| Feb 29, 2016 at 20:46 | comment | added | user145653 | Also, your examples of client-side languages are very reduced. Sticking always with the trio has become a little bit annoying. Moreover, saying that HTML isn't as primary (and nowadays CSS) as Javascript is completely unrealistic. Actually I would say that HTML is absolutely the first language of the web, and it's like that since the early nineties. | |
| Feb 29, 2016 at 20:43 | comment | added | user145653 | Your point under Uses "Interact with permanent storage (SQL, files)". SQL is a programming language, not a permanent storage. At most you can interact with databases through SQL. It would have been simpler if you had said just "databases". | |
| S Dec 30, 2015 at 17:58 | history | suggested | Community Bot | CC BY-SA 3.0 |
Adding another Server-Side language example
|
| Dec 30, 2015 at 15:16 | review | Suggested edits | |||
| S Dec 30, 2015 at 17:58 | |||||
| S Jan 12, 2015 at 15:09 | history | suggested | Michael | CC BY-SA 3.0 |
Minor fix to grammar and formatting
|
| Jan 12, 2015 at 15:03 | review | Suggested edits | |||
| S Jan 12, 2015 at 15:09 | |||||
| Oct 10, 2014 at 19:59 | comment | added | Madara's Ghost | It depends. Some client-side code depends on the existence of a server (prime example: AJAX). | |
| Oct 10, 2014 at 19:27 | comment | added | Juha Untinen | You could also say that Client-side code works even when you download the page and take it to a computer without internet access, while a Server-side code would never work in that scenario (unless you run a local server yourself). | |
| S Sep 1, 2013 at 9:28 | history | suggested | RyanJMcGowan | CC BY-SA 3.0 |
ASP is a deprecated language that has been replaced by ASP.Net framework which uses C# primarily as well as C++ and VB. Added non-website services to client-side languages so clarify that not all HTTP services are through a browser.
|
| Sep 1, 2013 at 8:32 | comment | added | RyanJMcGowan | I disagree with @ChrisMcCall's definition to a point. There could be exceptions to that rule, such as where a server might rely on a client to process data or provide a service to the server for the server to complete a task. Clients also are sharing an increasing amount of the load for scalability and performance such as in SPAs. These technologies blur that definition. A better definition could be that the end-user and the client are synonymous. It is expected that the end-user exists at the client device, whereas all other nodes would be considered server-side. | |
| Sep 1, 2013 at 8:17 | review | Suggested edits | |||
| S Sep 1, 2013 at 9:28 | |||||
| Oct 27, 2012 at 4:18 | vote | accept | Madara's Ghost | ||
| Oct 24, 2012 at 17:07 | comment | added | Madara's Ghost | So add it, feel free. | |
| Oct 24, 2012 at 16:28 | comment | added | stonemetal | I would add the fact that a server environment is more controlled. You have no idea what the client is. Also there are security concerns(for both parties) when doing things client side. | |
| Oct 24, 2012 at 15:04 | comment | added | Chris McCall | You fail to identify why the server is a server and the client is a client. The server is known about by the client, but not the other way around. The server is expected to be executing at all times, there are no client expectations. | |
| Oct 24, 2012 at 14:27 | history | edited | Madara's Ghost | CC BY-SA 3.0 |
Added clarification for HTML and CSS.
|
| Oct 24, 2012 at 14:25 | comment | added | FrustratedWithFormsDesigner | +1 for a good answer with examples of the uses! Just to nitpick: HTML and CSS are not actually programming languages, so they probably shouldn't be compared to "PHP, ASP, and Nearly any language (C++, C#, Java)". ActionScript might be another good example of a client-side language. | |
| Oct 24, 2012 at 14:21 | history | answered | Madara's Ghost | CC BY-SA 3.0 |