PHP vs .NET

Redline · 11-24-2004, 02:25 AM

I've wondered for a while, what if any, are the advantages of the .NET framework over PHP? I've looked at code snippets for PHP, C#, and ASP and all three seem to be capable of doing the same thing. I never got on this .NET wave, I've never quite understood it. Can someone explain to me what the major differences are, besides the obvious fact that Microsoft is behind .NET and pushing it like crazy? They are all server side scripting languages are they not? They all provide the possibility to create dynamic websites. They all allow you to process queries from several types of databases, they all allow you to read/write files and process all that information.

I'm asking this because I've wondered about .NET for quite a while, but also today I was told by a friend that if you really want to be successful in web design and server side programming you need to learn C#, and the rest of the .NET suite, not PHP. I've already learned PHP, it's an easy language to me now and I'm building on more and more programming concepts with it. If I can do it all with PHP, why would I be interested in learning .NET? I will probably learn it eventually, just to know it and be able to use it if I must.

Is my friend another brainwashed Microsoft junkie, or does he have a point?

I searched around a bit, and found this article - http://www.oracle.com/technology/pub.../hull_asp.html

It sounds to me like PHP and ASP.NET offer the same thing. And in addition, PHP offers quick bug fixes (open source), free implementation, better security for it's ability to run on Apache instead of IIS. There were some arguments against PHP for not being a true OOP model, but as of PHP5 it fully supports OOP. So I guess the answer to my question is; it's really just up to personal opinion and preference?

Belisarius · 11-24-2004, 06:10 AM

While this is more of the argument used for J2EE vs. PHP, I think it'll apply to .Net vs. PHP as well. PHP is a web scripting language. J2EE (and .Net as well) offer a wide range of networked data solutions, and as such are far more robust. They don't need to operate via webpages, they just can. Further, J2EE and .Net are designed to scale, which (and I'm just going on what others have told me here), PHP doesn't scale terribly well. For instance, could you cluster a PHP driven site?

Most people want to create mildly complex websites that have a database tie-in and maybe a couple other features. PHP was designed to tackle those problems. However, if you want a complex inventory control system that ties in to the production line to manage the rate at which specific products are created, and then automate the shipping process, I don't think PHP could do that. This is where other technologies, such as .Net and J2EE come in.

If you're just comparing ASP vs. PHP, then I'd say PHP will usually win hands down. But if you're comparing .Net vs. PHP, I just don't think PHP is robust enough to tackle the big problems that .Net was designed to tackle.