Why is javascript not part of the project architecture?

Question

I recently came across a question when someone asked which architecture we use in a company, and someone else answered LAMP.

I'm not sure why we are not including javascript as part of the architecture. Is that meant? Or am I missing something? What if someone uses an ECMA script or VB script instead of javascript?

Answer 1

Because "LAMP" only allows technologies that run on the server side, and not what runs on the client side, such as the browser or JavaScript in the browser. (And at the time LAMB was invented, JavaScript saw much less than it does today.)

Answer 2

JavaScript is a client technology, while Linux, Apache, MySQL, and Perl / Python / PHP are server related.

There are server-side JavaScript implementations, such as Aptana Jaxer and node.js , but JavaScript is most often used for browser behavior and, therefore, has little relation to the server, except through Ajax requests.

Answer 3

LAMP belongs to the main technologies used on the server side: Linux, Apache, MySQL and PHP. There are many other parts for installing LAMP, but they are either of secondary importance (for example, the bash shell), or they are client-side: HTML, JavaScript, CSS, etc.

Answer 4

LAMP is a server architecture.

On the Internet, HTML, JavaScript, and CSS were heavily relied upon to constitute the client architecture.

JavaScript is also an ECMAScript dialect with specific changes to the web browser.

Answer 5

Javascript is a web-based client technology. It can be activated or disabled by the user.