Okay, I've taken it upon myself to introduce the first PHP-based
application written for my work site. (Far be it for me to rock the
boat...) Anyway, I went about it this way. This will be hosted on our third (or fourth) Linux server (running SLES).
1. I spent a week writing up a replacement PHP/Apache/MSSQL application
which is faster and more customized than the vendors
JSP/JAR/XML/Tomcat/MSSQL application.
2. I showed it to my immediate supervisor and co-project manager, who both
had a cow and then conceded that it was a great idea.
3. We then showed it to our division manager who wasn't thrilled but agreed
it should be okay.
I thought things were just fine.
Today I find out that the "technology committee" has poo-poohed the idea.
This committee was formed of mostly mainframe guys and a few c/s guys, most of whom really only know VB/ASP. Senior management also takes part.
They don't see why we should be using PHP. They want JSP. In fact, they
don't know why we don't use JavaScript to write the whole application. (I
mentioned that there is - in fact javascript in a few of the pages to
handle form events, but that went over their heads.)
So here's my question. Given that they want me to use JSP, should I agree? In my opinion, I see more interest in PHP. In fact, I now notice that Big Blue is supporting PHP.
http://www-306.ibm.com/software/data...ndcore/pr.html
I particularly think that JSP is on the "outs" and that PHP will prevail
over JSP. They argue that I should be using Java, which I counter is a
server-side component to be used regardless of the scripting language.
What do you all think? Am I nuts? Okay, scratch that. Am I wrong in wanting
PHP over JSP?
Personally I like it better than JSP and feel it has a brighter future, especially since IBM is now pushing it. (We're an IBM
shop with an outgoing s390 and in incoming z890 and who knows how many AS400s.)