netsrek wrote:
> Is it also a factor because it is quicker to develop
using CF than PHP?
> Thanks
It can be, but PHP and CF don't match up 100% in what they
each do.
There are things that CF does faster|better|just plain PHP
can't do.
But it is the same in reverse, PHP does some things
faster|better|just
plain CF does not do.
So if your job is to do something PHP does that CF does not
do or does
not do well it is rather silly to use CF and vice a versa.
But of course there is a GREAT deal of overlap where they
both do the
same thing just fine. There are style differences that can
make one or
the other easier for any given individual to pick up.
But one of the factors that free|open source advocates tend
to overlook
is the cost of constantly searching for and evaluating
solutions. With
ColdFusion you get a great deal of add-ons and extra features
that have
fairly well been shown to work. Not perfect, of course, this
is
software. Stuff like Verity, cfimage, cfajax, cfpdf, cfhttp,
cfftp, ect.
In a PHP solution I would have to look for and often choose
from a wide
range of solutions and then test those solutions to make sure
they do
exactly what I need them to do and nothing else. Or recreate
the wheel
myself. With ColdFusion this has been done for me, and I have
a
specific entity (Adobe nee Macromedia nee Allaire) that I can
go to when
it does not work as advertised.
In the corporate world that relationship is worth a great
deal of money.
Especially in my previous position with a medical entity
where there
was the, at least theoretical, possibility that a software
bug could
kill somebody.