Web Development

Ask something
Discussion Locked

PHP Trust Issue

0 helpful
6 replies

by the_william

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi all,

I heard from a friend that a lot of companies today don't trust intranet application written in PHP. I was wondering if this is true? If it is, why?

Thanks!

Will

6 replies

by brent_d

if you have buisness logic, which you want to protect at all costs. But with asp, you can use custom components written in a VB and compiled into DLL's. So you have the advantage of compiled code which is faster then code produced by a web server, and DLL's are encrypted. AND you can re-use these custom components for other applications throughout the company

by bigdog

Granted php is not compiled but is scripted, however, just ask yahoo why it uses php in the enterprise environment? Just because the dlls are compiled does not mean that you are going to have a faster system. There are many (many) issues that go into performance besides compiled code.

by bigdog

PHP is widely used in intranets and extranets. I have work 2 years as a consultant on PHP projects that where only available on intranets.

by jimkunkel

There are pro-Microsoft bigots at least as "enthusiastic" as the pro-linux crowd. These guys have many years and a lot of money invested in Windows/IIS/SQL_Server/ASP, and are terrified of the effects of letting linux/Apache/PHP into the organization. And rightly so -- lower TCO, freedom from single sourced technology and from the license scheme of the month.

by smchris

>There are pro-Microsoft bigots at least as "enthusiastic" as the pro-linux crowd.

Since Oracle is shipping Apache and PHP with their products, this will probably become more recognized as a Microsoft vs. the World issue.

PHP may have started out with a poor support infrastructure as open source can before it matures. I know I was introduced to PHP by, what in retrospect, was a scornfully clueless professionally-published "3rd party"** book that taught one how to write fragile and terribly insecure PHP. Should never have passed through a technically competent editor even as an introduction because of the inherently poor programming practices it exampled. But it isn't like a sloppy book has never been published about using MS products either.

** open source can have "third party" publications too in the sense that I don't believe either author had anything to do with PHP project development.

by rmcvay

There are a number of reasons to pick one server parsed HTML platform or another but "trust" is no more a problem with PHP than with any other. I recommend that a group "goes with what it knows." If your web infrastructure is not pure Microsoft then PHP or CGI using Perl is the best way to go for simpler dynamic sites. If you're all Microsoft then ASP is a natural although there are probably more PHP-based apps like bulletin boards and such that would still lead you to that support on Windows.

This discussion is closed to new replies.