in reply to The REAL reason for why they choose PHP over Perl.

Hi Spidy,

<rant>
"The reports of my death have been greatly exaggerated." Mark Twain.

Did the instructor say anything along the lines of "C is a dead languague, its even older than Perl"? Or who will be doing the phasing out?
</rant>

This does not answer your question "why does everyone seem to prefer PHP nowadays?", but it is something to keep in mind. When I transferred from college to Uni our C++ teacher had written a book on the subject which we "Had to buy, if you want to stand a chance of passing this course". This was the same man who had no idea that you could compile C++ code using "Borland C++", nor could he explain the code he had 'written' for a linked list tutorial. In fact, I had to explain to that code to the class. What I am basically trying to point out is, just because someone is a boss, manager or 'educator' does not necessarily mean that they are right.

Cheers

Martin
  • Comment on Re: The REAL reason for why they choose PHP over Perl.

Replies are listed 'Best First'.
Re^2: The REAL reason for why they choose PHP over Perl.
by Spidy (Chaplain) on Jun 10, 2006 at 23:46 UTC
    Yeah, I've noticed that. However, even talking to people who are employed in the industry, they say they choose PHP "just 'cause", essentially. There are no real specific comments made as to why or why not PHP over Perl.
      Hi Spidy,

      I know people who earn their living using PHP/MySQL to build websites, and they too have the 'just because' reasoning behind their choice of languages. This is something I don't understand. I would like to think that when I make these sort of decisions, I am able to backup my decision based on facts and technical requirements, rather than just because I feel like implementing something using a particular language/technology. In my experience "the right tool for the right job" applys here, often various factors constrain the tools you can use in the work place. For example, some employers will stick to a tool/product set, be it ASP/MS SQL Server or PHP/MySQL, because their employees are skilled in these areas, or they have a lot of existing/legacy code in these languages which needs to be maintained.

      Martin
      That's fine by me. If they're making that sort of decision "just because" then I can expect them to be equally sloppy and slapdash in the other decisions they make and in the code they write. I don't want to work with such people. I'd be happy to be paid to clean up their mess afterwards though.

      And you never know, I might clean up their mess using Java or C or PHP instead of perl, if I think that that is the right choice.