Thoughts on several mainstream web development languages (I)

Original Web site: http://www.blogwind.com/Wuvist/comment.aspx? Article _id = 7245

When I started learning web development, I learned ASP.

Later, I always thought about PhP.

I have bought a lot of books, but unfortunately, I am stupid. I am always confused about installing PHP. Once I see that I need to manually modify the file and configuration, I think it is too big.

In contrast, in windows, playing ASP is too simple. Install IIS/PWS and run next.

For many Windows users, it is difficult to directly modify the configuration methods such as INI files, including me.

Or, let's say, PHP beginners will force ASP beginners to be so advanced. If you are playing with PHP, you will know how to install PHP on your own.

PHP installation is a learning process, or a very small threshold for entry ...... Some people may never be able to, or are unwilling to, cross-border.

However, there should also be some installation packages for Apache, PHP, and MySQL, which should be available all the way to next.

JSP is rarely used. Although occasionally curious about JSP, there is no reason to learn it.

Today, because I put a huge oolong, I finally took Tomcat 5.5.8 down, and now I can use JSP after next.

In addition, it seems to be Apache Tomcat.

Well, this may indicate that the "threshold" of the three website development languages ASP/PHP/jsp has become as low.

Asp.net is also almost low. Windows 2003 supports Asp.net by default, but ASP can be supported only after being set.

Or, I should divide it like this. asp and PHP (PHP 4, do not discuss PHP 5) belong to the same grade, while JSP and Asp.net are in another grade.

ASP and PHP are not actually called languages. They are only scripts and weak types of scripts.

They are both numbers and strings.

If the values of the variables A and B are all 1, should a + B be the "11" string or the number 2?

(I know Asp has & and PHP has. These two operators, but please take a look .)

In ASP/PHP, there is no strict control over these situations, and sometimes such problems will occur.

We often see that the end is similar to "? ASP/PHP beginners often make mistakes without verifying whether the ID is a number, which opens the door to SQL injection attacks.

This is because beginners have no experience or are lazy; but one of the root causes of this problem is that ASP/PHP is a weak language.

ASP/PHP are scripts, so they have powerful function libraries.

In many cases, the corresponding function name is called directly.

The code is short and concise.

After being familiar with ASP/PHP, You Can skillfully insert their code into HTML code to make a lot of wonderful dynamic web pages.

The combination of ASP/PHP and HTML code seems messy, but skilled ASP/PHP programmers do not feel confused. They know where to insert something, it is convenient to insert and mix code like this.

How can it be used?

However, it is very painful to try to use a chicken knife to kill cattle.

One of the reasons is that ASP/PHP are scripts and you cannot compile them.

Compile error/run time error/warrning and so on will not be known until the page you view in the browser.

In addition, the error message provided by the browser is not very useful.

Especially ASP, sometimes it is just a general 500 error. Developers cannot quickly know where the error is, and they can only rely on the experience of blood and tears.

"ASP will make people crazy" for a long time is my signature on various forums, which refers to this problem.

PHP is a little better than ASP, but it is only a little bit.

For example ......

By default, variables in ASP/PHP do not need to be declared.

It is automatically generated when you call it for the first time.

In the program, you accidentally compress the variable data or $ data into DETA or $ DETA.

When the wrong variable name is hidden in hundreds of lines of code, you may be so mad that you cannot find it.

ASP and PHP have their own supporters.

I personally think PHP is better.

The first reason is: <?> Easier to enter than <%>.

I don't know whether the ASP/asp.net/jspdesigners of tiankill want to choose from the following: <%>.

Second, PHP uses more function libraries than ASP by default.

At least, it can process file uploads. ASP requires components, or writes the upload class without components.

For scripts such as ASP and PHP, the richness of function libraries is very important. It determines what you can do and what you cannot do. I mean, not everyone knows how to write ASP's component-less upload class.

I am referring to the default function library. Most ASP/PHP developers use virtual hosts. They cannot ask the service provider to install the components/extension they need on the server.

After adding components/extension support to ASP and PHP, there will be a lot of work to be done and there will be no way to compare them.

Third, default database support.

ASP generally uses access, while PhP uses MySQL.

For web development, the database is crucial. It also determines the scope of what you can do.

A website with tens of thousands of IP addresses per day cannot be implemented using ASP + access. Access cannot support such an order of visits. MySQL does not have this problem.

With ASP + access web site bigger after, must be transferred to other databases, for example, ms SQL. The number of PHP + MySQL websites that need to be migrated to PHP + oracle is rare. This transfer may not happen, even if it appears, it will be much later than the transfer from access to ms SQL.

It is not to say that access is not competing, but that access is not intended for websites. Access-based programmers and ASP + Access-based programmers have two different concepts.

Microsoft's database product, ms SQL, and access, should have one more thing. This thing should be MSDE ...... The problem is that MSDE has come out late and is not widely used. Microsoft seems to have never promoted MSDE.

If ASP + MSDE is widely used for website development instead of ASP + ACCESS, I Would Like ASP more.

(I guess. I don't know MSDE .)