Web browsers Client-side scripting Web browsers are applications for displaying web pages.
A scripting language is usually interpreted from source code or bytecode. By contrast, the software environment the scripts are written for is typically written in a compiled language and distributed in machine code form; the user may not have access to its source code, let alone be able to modify it.
The first interactive shells were developed in the 1960s to enable remote operation of the first time-sharing systems, and these used shell scripts, which controlled running computer programs within a computer program, the shell.
General-purpose dynamic languages See also: Dynamic programming language Some languages, such as Perl, began as scripting languages but were developed into programming languages suitable for broader purposes.
(In this sense, one might think of shells as being descendants of IBM's JCL, or Job Control Language, which was used for exactly this purpose.) Many of these languages' interpreters double as command-line interpreters such as the Unix shell or the MS-DOS COMMAND.COM.
Embedding of such general purpose scripting languages instead of developing a new language for each application also had obvious benefits, relieving the application developer of the need to code a language translator from scratch and allowing the user to apply skills learned elsewhere. GUI scripting With the advent of graphical user interfaces, a specialized kind of scripting language emerged for controlling a computer. These languages could in principle be used to control any GUI application; but, in practice their use is limited because their use needs support from the application and from the operating system.
Client-side scripts are sent by the server "as-is" and are run by the client's computer. Other applications embedding ECMAScript implementations include the Adobe products Adobe Flash (ActionScript) and Adobe Acrobat (for scripting PDF files).
]Text processing languages The processing of text-based records is one of the oldest uses of scripting languages. Emacs Lisp, while a fully formed and capable dialect of Lisp, contains many special features that make it most useful for extending the editing functions of Emacs.
Scripts can be run by web browsers to change the appearance or behaviour of a web page, for example, to change the content to be specific to the current user.Early mainframe computers (in the 1950s) were non-interactive, instead using batch processing.
Multics calls these active functions. Louis Pouzin wrote an early processor for command scripts called RUNCOM for CTSS around 1964.
|Client Scripting||Server Scripting|
Client side scripting can access files and settings that are local at the user computer.
Client side scripting consumes cycles from user's computer not web server one, while server side scripting consumes cycles form web server one
Server side scripting, (ex. ASP.Net, ASP, JSP, PHP, Ruby, or others), is executed by the server (Web Server), and the page that is sent to the browser is produced by the serve-side scripting.
So when a server sends out a page, it executes server-side scripts, but does not execute client-side scripts. Once the browser receives the page, it executes the client-side scripts.
Server side scripting can connect to databases that reside on the web server or another server reachable from web server. Client side scripting cannot do that.
Server side scripting can access the file system that reside at the web server, client side cannot.
Server side scripting can access settings belong to Web server while client side cannot.