|
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.
|