PHP vs JSP vs ASP.NET

Hey all.

I’m curious about comparing the three subject technologies (if it is possible) in terms of speed.
I understand that they are intended to solve different tasks, but still if one of the main criteria for me is the robustness (execution speed) of end-application (and the application is not very large), what should I use? Any ideas?

Thanks in advance.

As a developer you main goal is to provide the client with the most logically sound application. So that means that no one technology will ever suffice to provide that. If you program in all of those languages you should then know that each is capable in providing the tools to develop most any application that is resource friendly and truly adequate in handling any type of speedy remote access. If it’s personal application, then use the technology that you understand the best, as that reasoning is most likely always the best way to proceed.

Thanks.

Understanding the meaning of development you understand all the technologies, no matter how complex it is. But the issue is at some stage to make a decision between some in terms of current requirements. So I’m curious, what is the field that php is faster for processing, what for java and ASP.NET. I mean faster at runtime, not at development time, and I mean only the speed, I don’t mean security, development tools…

Maybe that is quite a BIG issue and is a matte of writing a book, but still maybe there are some basic considerations?

Thanks.

Umm! golotyuk, I would ask this question separately in different sites/forums of those languages how faster they are.

  1. Why should i use PHP? //php forum like sitepoint
  2. Why should i use JSP? //java forum
  3. Why should i use ASP.NET? // asp.net forum

Then make a conclusion by comparing three language’s aspects.

Lol!

I can’t say about JSP and ASP.NET so I did not explain about PHP too because i thought to be more clear yourself about PHP.

PHP is simple, fast and very powerful.

ASP.NET is more complex, slower, but more powerful

JSP - I can’t say.

Rajug, all of the forums for these languages are also in sitepoint.

Thanks :slight_smile:
Already did that. I don’t think that is quite accurate info, because any community is fond of their stuff including programming language.

The most frequent answer I get is - you need to decide that closer to requirements. Java - is enterprise software development tool… bla… .NET - is almost the same, but not so widespead, PHP - is for small tasks. But nobody talks about the speed, if assumed that I can solve pretty small task in all of them and compare it.

I think I should install IDEA, MS Visual Studio as well as Zend, and try myself :slight_smile:

Oh boy, this is going to be another one of those threads.

Since the original question is about execution speed, I’ll stick solely with that. JSP and .NET both get compiled to byte-code so theoretically, it should be faster. However, there are multiple PHP byte-code compilers that cache the byte-code. As a matter of fact, PHP 6 will have the APC built-in. So, to the best of my knowledge, PHP is faster. However, I am not an expert on JSP or .NET.

Like anything that you will encounter regarding programming, one should never think about speed as the motive of development. The reason why is that each language will never be overly faster than another. To understand that comment look at this way. If language A, can solve problem A faster than language B or C, does that mean it will be faster solving problem B. No, never is that case, so as I said, developers should understand that no one language will solve all problems in the most resource friendly way. So that means you are left with (2) development choices. (1), use different languages for different tasks, like if it’s back end related and needs the best text manipulation logic, go for Perl, because nothing matches Perl’s understanding of manipulating text and it’s open source library’s provide access to those powerful text manipulating tools, which cuts development time. So you get fast development with true Unicode support to accomplish the task at hand. Now would I use Java, PHP, ASP/.NET, to do that, no, never, they are not designed to do that in the way Perl can.

Now I want to create a front end, I can use (ASP, PHP, Perl, .NET, Java), now I think about what I am doing, so I say to myself, I am going to build a chat, or maybe a multi player game system (Java, rules here), or I am going to build a system that needs XML support (ASP/.NET). Just imagine trying to build a chat system in PHP or Perl or even .NET, you will only create a nightmare and nothing else. Then you might say, why use (ASP/.NET), doesn’t (PHP, Perl, Java) support XML. Yes they do, but PHP doing XML is like the worse thing you could ever try to develop, because while PHP can hack XML, it can’t give you the true unique ways of accomplishing a task like (.NET), because the (.NET) model is designed around SOM model, which is the richest API one could hope to have in their development drawing board. (If you don’t believe me, check out PHP’s C source in regards to it’s XML extensions, they are pure silliness) That not to say I even like XML, as that data storage model goes against every easy accessible fundamental one could try to dream up. The best data storage model is the SQL storage model (Ted Codd), no database today even comes close to using it, but even the most primitive database used today has better access methods than anything XML provides.

So basically, choice (1) says that you create an application based on the best tool for the job. Which gives you the best over all design, that will be the most feature rich and truly resource friendly. Choice (2), is the back yard mentality, where you limit your development to what you know, there is nothing wrong with that, it just means your application will never be the best it really could be. With that said, is choice (2) wrong? No, not necessarily. Because the application will be able to do what you need it to do, and you will know how to work on it, so you will be able to improve it through time. But that brings us back to the question, “does speed matter”, yes, but why even talk about it when most developers live with choice (2)!

well said.

I’m not quoting you directly, but rather to clarify that asp.net is simple, fast as hell and more powerful.

:slight_smile: