Xarzu Thompson wrote:What are the pros and cons of plain PHP or Classic ASP?
Any attempt at making such a list is invariably going to be incomplete and vague. I can only offer you a very broad comparison of server-side versus client-side applications.
Client-side applications have the advantage that they can update the user interface without reloading the page.
Server-side applications have the advantage that they run "privately", meaning the user can't see or alter the code or the data that the code is running on.
"Wrong" depends on the purpose of the website. A site written completely in a server-side language will not be able to update the user interface except through page reloads. If your application state rarely changes as a result of user input (for example, when your website is purely informational, such as an encyclopedia, user manual or educational pamphlet) then you don't need any client-side code except for the static HTML.
If on the other hand you want your user interface to react to user-input responsively, using only server-side code is not going to cut it. Another drawback is that validating user input on the server-side without pre-validating it on the client can put undue strain on a server. If you can validate user input on the client side and prevent a round-trip when the user has input invalid data, do it. However, even if you validate user input on the client-side, you must ALWAYS validate it on the server-side a second time to prevent tampering.
Your question implies that it is not uncommon to write an application completely in client-side code. This is not the case. Almost every web application will interact with a server, in which case you will need at least *some* server-side code. Applications written completely in client-side code are typically simple tools such as calculators or encoders/decoders, or single player games.
bring to the table. I explained this earlier.
All I know right now is that it is written in PHP and Classic ASP. I am in the process of investigating these scripting languages and I want to know what the opinion of other developers are.
Don't call them scripting languages. The phrase "scripting language" is meaningless. Call them "programming languages" or just "languages".
There's not much to say here. If the website you have to maintain doesn't use client-side programming, it won't be able to react to user-input responsively. If the website doesn't take (much) user input, it might not even need client-side programming.