Comments on: Why PHP Is BETTER Than ASP/ASP.NET http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/ Linux. GNU. Freedom. Mon, 01 Dec 2008 22:08:50 +0000 http://wordpress.org/?v=2.7-almost-rc-9997 hourly 1 By: doug http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-108916 doug Wed, 26 Nov 2008 15:16:58 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-108916 can anyone name a website valued in the nine figures developed with .net? i can't think of one. but digg, facebook, flickr, youtube, etc. are all lamp (php) sites. can anyone name a website valued in the nine figures developed with .net?

i can’t think of one.

but digg, facebook, flickr, youtube, etc. are all lamp (php) sites.

]]> By: asdasd http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-108908 asdasd Thu, 20 Nov 2008 10:23:26 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-108908 "The character that the browser uses to recognize PHP code from regular HTML code is the ‘?’ " The browser doesn't see the PHP code “The character that the browser uses to recognize PHP code from regular HTML code is the ‘?’ ”

The browser doesn’t see the PHP code

]]> By: Andy http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-108857 Andy Sun, 26 Oct 2008 15:19:42 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-108857 Personally, I don't think technology itself can decide which is better and which is not. An application is written by the developer, as so the end product is actually the design of the developer. Some people wrote good application in PHP and some don't that's the fact, and it goes the same for ASP.Net. It becomes useless to benchmark these technologies, when you have finish reading this post, some developer (in any part of the world) might have already finish developing an application. Personally, I don’t think technology itself can decide which is better and which is not. An application is written by the developer, as so the end product is actually the design of the developer. Some people wrote good application in PHP and some don’t that’s the fact, and it goes the same for ASP.Net. It becomes useless to benchmark these technologies, when you have finish reading this post, some developer (in any part of the world) might have already finish developing an application.

]]> By: PHP Coder http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-106934 PHP Coder Tue, 26 Aug 2008 12:18:50 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-106934 I program both in PHP and ASP.NET. From my experience, i can say that asp.net is better in performance and it has been targetted to new and _lazy_ developers. It provides too many features - which i just don't like. For this reason i have dropped asp.Net and started with php. Asp.Net is good for starters. Asp.Net is so easy that anyone can create a website and this potentially can lead to programers unemployment! I program both in PHP and ASP.NET. From my experience, i can say that asp.net is better in performance and it has been targetted to new and _lazy_ developers. It provides too many features - which i just don’t like. For this reason i have dropped asp.Net and started with php. Asp.Net is good for starters. Asp.Net is so easy that anyone can create a website and this potentially can lead to programers unemployment!

]]> By: um http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-104114 um Tue, 08 Jul 2008 19:01:35 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-104114 php is better than c# because you would rather use the ? over the %... Ya, that's def the deciding factor when I choose a language for a project... wow. php is better than c# because you would rather use the ? over the %… Ya, that’s def the deciding factor when I choose a language for a project… wow.

]]> By: Hesham Omran http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-103878 Hesham Omran Wed, 02 Jul 2008 11:08:40 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-103878 Hey Guys, nice posts. you ppl are taking things personally somehow... kiddin. anywayz I just wanted to tell you about my experience, I was a PHP developer during the times at my university, I owe PHP as it's my first language for web programming, and actually I was with the GO PHP 5 movement, and I decided that I will be object oriented. but then I had to work with ASP.NET for an internship. and I fell in love. maybe PHP is faster, I noticed it as an observer on single page level, I don't know on stress testing what would happen, but ASP.NET is a rapid Development Framework and language. such as authentication and authorization, membership providers that has a very flexible degree of customization. a whole lot of support, such as Code Project community. Microsoft MVPs across the internet writing articles and making controls. and NetTiers a Tier design code generator, maybe I was more lucky to find parallel solutions to help me develop faster than PHP. finally, maybe if PHP would get a unified framework around it and good IDE that really make things easier I would return back. and believe me I am searching all I got is a IDE from here like PHP designer and framework from there like PradoSoft, Zend or others, a template based generator like smarty... but the end it became a mess and somehow a spagetti. and I know u will tell me ZEND Framework and IDE is for that purpose, but my Zend experience was very bad and it's not optimized for PHP OOP. maybe what made ASP.NET better is the IDE and .NET Framework, one framework everybody can base their work on it, one big solution rather than many small solutions. This is just an opinion of mine Thank you Hey Guys, nice posts. you ppl are taking things personally somehow… kiddin. anywayz I just wanted to tell you about my experience, I was a PHP developer during the times at my university, I owe PHP as it’s my first language for web programming, and actually I was with the GO PHP 5 movement, and I decided that I will be object oriented. but then I had to work with ASP.NET for an internship. and I fell in love. maybe PHP is faster, I noticed it as an observer on single page level, I don’t know on stress testing what would happen, but ASP.NET is a rapid Development Framework and language. such as authentication and authorization, membership providers that has a very flexible degree of customization. a whole lot of support, such as Code Project community. Microsoft MVPs across the internet writing articles and making controls. and NetTiers a Tier design code generator, maybe I was more lucky to find parallel solutions to help me develop faster than PHP. finally, maybe if PHP would get a unified framework around it and good IDE that really make things easier I would return back. and believe me I am searching all I got is a IDE from here like PHP designer and framework from there like PradoSoft, Zend or others, a template based generator like smarty… but the end it became a mess and somehow a spagetti. and I know u will tell me ZEND Framework and IDE is for that purpose, but my Zend experience was very bad and it’s not optimized for PHP OOP.

maybe what made ASP.NET better is the IDE and .NET Framework, one framework everybody can base their work on it, one big solution rather than many small solutions.

This is just an opinion of mine

Thank you

]]> By: Dan http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-103116 Dan Tue, 17 Jun 2008 16:56:15 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-103116 I own a web development firm that started off as 3 people. 2 years ago we offered both ASP.net and PHP but decided that if we wanted to be good at either one we would have to drop one and use just the other. That is when we decided to go with PHP and drop ASP.net. The reasons behind our decision is conclusive on many of your posts above. When developing good web applications we are more concerned about the final output for our customers sake and not the fact that we saved the programmer an extra day because we made his life a bit more efficient. We want our websites to be custom built specifically for our customers and not carry any unnecessary overhead like ASP.net does. After researching this for about 2 years we decided PHP was the best option for our company. Today we have 12 employees and have been the fastest growing company in our city for two years in a row. Our customers notice the quality of our work and their websites and they keep coming back for more. In the end, that is what really matters. To end this argument, it's really not about giving the programmers what they need at the expense of the customer's website performance or visual layout. It's about making sure that the customers website runs to the best of it's ability for years to come. With PHP it is possible, and for Tom who wrote the very long article about ASP.net. We do have all of those features in our PHP web applications. Maybe you should visit zend.com and read a little bit more about enterprise level PHP. I own a web development firm that started off as 3 people. 2 years ago we offered both ASP.net and PHP but decided that if we wanted to be good at either one we would have to drop one and use just the other. That is when we decided to go with PHP and drop ASP.net. The reasons behind our decision is conclusive on many of your posts above. When developing good web applications we are more concerned about the final output for our customers sake and not the fact that we saved the programmer an extra day because we made his life a bit more efficient. We want our websites to be custom built specifically for our customers and not carry any unnecessary overhead like ASP.net does. After researching this for about 2 years we decided PHP was the best option for our company. Today we have 12 employees and have been the fastest growing company in our city for two years in a row. Our customers notice the quality of our work and their websites and they keep coming back for more. In the end, that is what really matters. To end this argument, it’s really not about giving the programmers what they need at the expense of the customer’s website performance or visual layout. It’s about making sure that the customers website runs to the best of it’s ability for years to come. With PHP it is possible, and for Tom who wrote the very long article about ASP.net. We do have all of those features in our PHP web applications. Maybe you should visit zend.com and read a little bit more about enterprise level PHP.

]]> By: Craig http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-98667 Craig Wed, 23 Apr 2008 05:21:03 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-98667 Oh...My...God... Not only have you managed to simplify the entire inefficiency and bad design of ASP and .NET down to the bad design used in the tags, but you've blown my mind with how true it is! In regards to Tom's rather long-winded comment: You seem to be showing why ASP.NET is better than classic ASP. That's kind of a given. Your extensive list of features is great, but if you think these are things PHP isn't capable of, you have A LOT of research to do. With a little bit of knowledge (which most PHP developers obviously already have, otherwise they would be using ASP) it's not at all difficult to replicate any / all of those fancy ASP features, and without paying! Being able to use multiple languages is not a good thing. It's actually a major problem with ASP.NET, as it means there is no real standardisation. Oh…My…God…
Not only have you managed to simplify the entire inefficiency and bad design of ASP and .NET down to the bad design used in the tags, but you’ve blown my mind with how true it is!

In regards to Tom’s rather long-winded comment:
You seem to be showing why ASP.NET is better than classic ASP. That’s kind of a given.
Your extensive list of features is great, but if you think these are things PHP isn’t capable of, you have A LOT of research to do. With a little bit of knowledge (which most PHP developers obviously already have, otherwise they would be using ASP) it’s not at all difficult to replicate any / all of those fancy ASP features, and without paying!
Being able to use multiple languages is not a good thing. It’s actually a major problem with ASP.NET, as it means there is no real standardisation.

]]> By: Tom http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-92295 Tom Sun, 24 Feb 2008 00:58:13 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-92295 Wow, I have to say that I am quite suprised. The idiocracy of trying to say that PHP is better than ASP.NET. For certian small websites, sure, use PHP. I own a company that develops software. All we use is ASP.NET... and here is why: It provides an entirely new programming model for creating network applications that take advantage of the Internet. Improved Performance and Scalability • Compiled Execution: ASP.NET is much faster than classic ASP, while preserving the "just hit save" update model of ASP. No explicit compile step is required. ASP.NET automatically detects any change, dynamically compiles files if needed, and stores the compiled results to reuse for subsequent requests. Dynamic compilation ensures that your application is always up to date, and compiled execution makes it fast. Most applications migrated from classic ASP to ASP.NET see a 3x to 5x increase in pages served. • Rich Output Caching: ASP.NET output caching can dramatically improve the performance and scalability of your application. When output caching is enabled on a page, ASP.NET executes the page once and saves the result in memory before sending it to the user. When another user requests the same page, ASP.NET serves the cached result from memory without re-executing the page. Output caching is configurable, and it can be used to cache individual regions or an entire page. • Web Farm Session State: ASP.NET session state lets you share session data across all machines in a Web farm. Now a user can hit different servers in the Web farm over multiple requests and still have full access to session data. Enhanced Reliability • Memory Leak, Dead Lock, and Crash Protection: ASP.NET automatically detects and recovers from errors such as dead locks and memory leaks to ensure that your application is always available. For example, when a memory leak is detected, ASP.NET automatically starts up a new copy of the ASP.NET worker process and directs all new requests to the new process. After the old process has finished processing pending requests, it is gracefully disposed of and the leaked memory is released. Easy Deployment • "No Touch" Application Deployment: With ASP.NET you can deploy an entire application by copying it to the server. Configuration settings are stored in an XML file within the application. • Dynamic Update of Running Application: ASP.NET lets you update compiled components without restarting the Web server. Unlike classic COM components that required the Web server to be manually restarted when an update was deployed, ASP.NET automatically detects the change and starts using the new code. • Easy Migration Path: ASP.NET runs side by side on IIS with classic ASP applications on Microsoft Windows 2000 and Windows XP, and on members of the Windows Server 2003 family. You can migrate one application at a time, or even single pages. ASP.NET even lets you continue to use your existing classic COM business components. New Application Models • XML Web Services: XML Web services allow applications to communicate and share data over the Internet, regardless of operating system or programming language. ASP.NET makes exposing and calling XML Web services simple. • Mobile Web Device Support: ASP.NET mobile controls let you target over 80 mobile Web devices using ASP.NET. You write the application once, and the mobile controls automatically generate pages for the requesting device. Developer Productivity • Easy Programming Model: ASP.NET makes building real-world Web applications dramatically easier with server controls that let you build great pages with far less code than classic ASP. • Flexible Language Options. ASP.NET supports not only Microsoft Visual Basic Scripting Edition (VBScript) and Microsoft JScript but also more than 25 .NET languages, including built-in support for Visual Basic .NET, Microsoft C#, and JScript .NET. • Rich Class Framework: The .NET Framework class library offers over 4,500 classes that encapsulate rich functionality such as XML, data access, file upload, regular expressions, image generation, performance monitoring and logging, transactions, message queuing, and SMTP mail. Now when compared to PHP there is no comparison! Wow, I have to say that I am quite suprised. The idiocracy of trying to say that PHP is better than ASP.NET. For certian small websites, sure, use PHP. I own a company that develops software. All we use is ASP.NET… and here is why:

It provides an entirely new programming model for creating network applications that take advantage of the Internet.

Improved Performance and Scalability
• Compiled Execution: ASP.NET is much faster than classic ASP, while preserving the “just hit save” update model of ASP. No explicit compile step is required. ASP.NET automatically detects any change, dynamically compiles files if needed, and stores the compiled results to reuse for subsequent requests. Dynamic compilation ensures that your application is always up to date, and compiled execution makes it fast. Most applications migrated from classic ASP to ASP.NET see a 3x to 5x increase in pages served.

• Rich Output Caching: ASP.NET output caching can dramatically improve the performance and scalability of your application. When output caching is enabled on a page, ASP.NET executes the page once and saves the result in memory before sending it to the user. When another user requests the same page, ASP.NET serves the cached result from memory without re-executing the page. Output caching is configurable, and it can be used to cache individual regions or an entire page.

• Web Farm Session State: ASP.NET session state lets you share session data across all machines in a Web farm. Now a user can hit different servers in the Web farm over multiple requests and still have full access to session data.

Enhanced Reliability
• Memory Leak, Dead Lock, and Crash Protection: ASP.NET automatically detects and recovers from errors such as dead locks and memory leaks to ensure that your application is always available. For example, when a memory leak is detected, ASP.NET automatically starts up a new copy of the ASP.NET worker process and directs all new requests to the new process. After the old process has finished processing pending requests, it is gracefully disposed of and the leaked memory is released.

Easy Deployment
• “No Touch” Application Deployment: With ASP.NET you can deploy an entire application by copying it to the server. Configuration settings are stored in an XML file within the application.

• Dynamic Update of Running Application: ASP.NET lets you update compiled components without restarting the Web server. Unlike classic COM components that required the Web server to be manually restarted when an update was deployed, ASP.NET automatically detects the change and starts using the new code.

• Easy Migration Path: ASP.NET runs side by side on IIS with classic ASP applications on Microsoft Windows 2000 and Windows XP, and on members of the Windows Server 2003 family. You can migrate one application at a time, or even single pages. ASP.NET even lets you continue to use your existing classic COM business components.

New Application Models
• XML Web Services: XML Web services allow applications to communicate and share data over the Internet, regardless of operating system or programming language. ASP.NET makes exposing and calling XML Web services simple.

• Mobile Web Device Support: ASP.NET mobile controls let you target over 80 mobile Web devices using ASP.NET. You write the application once, and the mobile controls automatically generate pages for the requesting device.

Developer Productivity
• Easy Programming Model: ASP.NET makes building real-world Web applications dramatically easier with server controls that let you build great pages with far less code than classic ASP.

• Flexible Language Options. ASP.NET supports not only Microsoft Visual Basic Scripting Edition (VBScript) and Microsoft JScript but also more than 25 .NET languages, including built-in support for Visual Basic .NET, Microsoft C#, and JScript .NET.

• Rich Class Framework: The .NET Framework class library offers over 4,500 classes that encapsulate rich functionality such as XML, data access, file upload, regular expressions, image generation, performance monitoring and logging, transactions, message queuing, and SMTP mail.

Now when compared to PHP there is no comparison!

]]> By: Ben http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-88116 Ben Mon, 07 Jan 2008 16:18:48 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-88116 PHP or perl i dont mind, cold fusion/jsp (never used) and the new visual studio.net products (every release is just excuse for microsofts profits). I like PHP cos its free and they dont care about profits and have full user support! PHP or perl i dont mind, cold fusion/jsp (never used) and the new visual studio.net products (every release is just excuse for microsofts profits). I like PHP cos its free and they dont care about profits and have full user support!

]]> By: Nicolas http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-84844 Nicolas Tue, 18 Dec 2007 16:09:24 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-84844 to keep people busy a far longer time solving a trivial problem with shitloads of objects and crap that is inherently not needed to solve the problem algorithmically. Procedurally always suffices, or does anyone of you here think the code of an usual business app requires more logic than quake 3? (plain c) ... or the freebsd kernel components (also plain c)... or huge parts of windows nt (guess what)... OOP is almost always inefficient, and most useful code written in "OOP" languages (that try to force you into using the concept) has also mostly procedural structures. It's the way computers work at the end, goddamnit. Not one single object in assembler, nothing. to keep people busy a far longer time solving a trivial problem with shitloads of objects and crap that is inherently not needed to solve the problem algorithmically. Procedurally always suffices, or does anyone of you here think the code of an usual business app requires more logic than quake 3? (plain c) … or the freebsd kernel components (also plain c)… or huge parts of windows nt (guess what)… OOP is almost always inefficient, and most useful code written in “OOP” languages (that try to force you into using the concept) has also mostly procedural structures. It’s the way computers work at the end, goddamnit. Not one single object in assembler, nothing.

]]> By: Gunjan http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-84302 Gunjan Sat, 15 Dec 2007 19:12:30 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-84302 PHP is better than .net but why .net opening are more than PHP in the market? PHP is better than .net but why .net opening are more than PHP in the market?

]]> By: Nicolas http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-84211 Nicolas Sat, 15 Dec 2007 09:32:56 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-84211 I've been an active PERL / Unix dev for 2 years now, was on .net hysteria before. I find the best language of .net to be vb.net, and even this particular one sucks so extremely hard... why do we need a fucking object for every @½"*+ç little operation? MS pumps up the complexity absolutely artificially. There is nothing you cannot do with plain C, as it's the 3rd generation lang that is closest to asm.. the farer a programming language derives from expressing the true inner workings of a computer, the more likely it is that it gets into your way. I hate OOP therefore. I disliked it before but I started to REALLY hate it when I saw that basically everything is just a pointer to some memory region... as a programmer, you issue simple commands on these, no matter what language you use.. so why not use one that *doesn't* hide the *way it really works* from you? Flexibility increases as well as productivity. PHP has a sane level of abstraction, perl even better, c#/vb.net/java (no pointers? wtf why?) and even c++ for that matter have not. MS generally releases few useful pieces of software, I consider windows as well as directx to be amongst them. Definitely not asp.net and the MS sql server neither. I’ve been an active PERL / Unix dev for 2 years now, was on .net hysteria before. I find the best language of .net to be vb.net, and even this particular one sucks so extremely hard… why do we need a fucking object for every @½”*+ç little operation? MS pumps up the complexity absolutely artificially. There is nothing you cannot do with plain C, as it’s the 3rd generation lang that is closest to asm.. the farer a programming language derives from expressing the true inner workings of a computer, the more likely it is that it gets into your way. I hate OOP therefore. I disliked it before but I started to REALLY hate it when I saw that basically everything is just a pointer to some memory region… as a programmer, you issue simple commands on these, no matter what language you use.. so why not use one that *doesn’t* hide the *way it really works* from you? Flexibility increases as well as productivity. PHP has a sane level of abstraction, perl even better, c#/vb.net/java (no pointers? wtf why?) and even c++ for that matter have not.

MS generally releases few useful pieces of software, I consider windows as well as directx to be amongst them. Definitely not asp.net and the MS sql server neither.

]]> By: Larry http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-81081 Larry Thu, 29 Nov 2007 05:43:43 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-81081 What developer wants a server-side technology that decides what HTML/XHTML it's going to output? Only the ones that don't care (or don't understand) proper XHTML. And I certainly don't want a billion CSS classes for every element! That's reason enough for me to move to PHP. Give me clean and semantic markup please. Oh, do any of you even know what semantic means? Didn't think so! What developer wants a server-side technology that decides what HTML/XHTML it’s going to output? Only the ones that don’t care (or don’t understand) proper XHTML.

And I certainly don’t want a billion CSS classes for every element! That’s reason enough for me to move to PHP. Give me clean and semantic markup please. Oh, do any of you even know what semantic means? Didn’t think so!

]]> By: Ben http://pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-80083 Ben Fri, 23 Nov 2007 03:21:43 +0000 http://www.pthree.org/2006/01/11/why-php-is-better-than-aspaspnet/#comment-80083 As a young developer, very new to the field of web applications, I have come to agree with those who prefer PHP. However, I have very little room to speak, as I only know PHP, and have just begun. Who knows, I may eventually be persuaded into using .NET more after I learn it. To digress a tad, I would like to add an observation that may or may not be actual or truthful. It seems that the majority of people who know .NET also know C++ or some other language. This makes me believe that PHP will come out the victor for the simple fact that their is no other language requirement. People who want to become a web-developer(applications, pages, etc.), would probably choose PHP for its simplicity and ability to be learned quicker. Performance wise, I can not judge as I have not tested either but it seems like milliseconds. Development wise, I can not judge as well because I have not used .NET, only PHP, so I am biased. From what I have seen, it can be more indepth than PHP but also be overcomplicated. ~Ben As a young developer, very new to the field of web applications, I have come to agree with those who prefer PHP. However, I have very little room to speak, as I only know PHP, and have just begun. Who knows, I may eventually be persuaded into using .NET more after I learn it.

To digress a tad, I would like to add an observation that may or may not be actual or truthful. It seems that the majority of people who know .NET also know C++ or some other language. This makes me believe that PHP will come out the victor for the simple fact that their is no other language requirement. People who want to become a web-developer(applications, pages, etc.), would probably choose PHP for its simplicity and ability to be learned quicker.

Performance wise, I can not judge as I have not tested either but it seems like milliseconds.
Development wise, I can not judge as well because I have not used .NET, only PHP, so I am biased. From what I have seen, it can be more indepth than PHP but also be overcomplicated.

~Ben

]]>