As an experienced PHP programmer, I'd HIGHLY recommend coders, especially beginners, tick with PHP version 4. I know its tempting to get the 'latest and greatest', however, v5 is still too new, and the majority of servers out there still only support v4 code, so you will run into problems if you already start using functions/methods available in v5 only, and dont own/operate/have root on the server in which your code is going to run, and only ever run.
I don't plan to make the switch to version 5 for at le
You're right in some ways, but I'd hate to tell someone to stick to php4 when php5 is so much better. 1and1.com [1and1.com] offers php5 support already...
just spreading the word, I'm sure there are others, but that's what I know for sure.
And if you are in control of your own server, you can keep php4 + apache running in the foreground and then ProxyPass to a second apache running on a diff port if you want to start deploying some php5 apps until you are confident you can move everything over to php5.
Not sure I'd agree with php5 being "so much better". and just a handful of web hosting companies supporting php5 doesnt make it the defacto as I said.
Portability is really the key here, and in sticking with php4 code, everyone can save headaches from not knowing why certain (php5 only) functions arent working when they "should be". Which mostly just a function of experience. However php is growing very fast in popularity, and because of that, keeping the code as portable as possible is always the best ch
Heh.. maybe we agree to disagree.. because I am pretty sure that php5 is "so much better":-)
The better object model and the try / catch additions alone are what, to me, really sells it
I'm not saying that your points are not valid.. they are.. portability is sometimes key.. and yes, if it needs to move and run in many different environments, I guess you might choose php4. If you don't have control of your production environment, then you have to code to what is there, to be sure, but if I'm in con
So then what happens is later, that client decides they want to switch the system/code you wrote to a different hosting provider, which doesnt support php 5?
Have fun with that support call.
And yes, there are some providers taht still have mysql 3.x, however, mysql 4 is the norm, and on MOST servers, which was my point to begin with.
And no, I dont think that PHP 5 is production ready yet either, at least I wouldnt take that chance if I was building for paying clients.
Hah.. yeah, that would be an interesting support call to say the least.
Truth of the matter is that I don't think that responsibility falls in my lap. A system is built to a certain requirement spec at the time of proposal... we need x,y,z to be in place and we'll give you a,b,c... if you decide to move to a place that doesn't support the reqs of the original project, how is this my problem?
What if we built a java web app and the person sometime down the road wants to switch to a different server/provider that doesn't have java installed/supported? Is that really much different?
In the course of the past 4 months, we've acquired (or upgraded to their new server offerings) about 4 different root servers from 4 different providers
ValueWeb
1and1.com
MediaTemple
Verio
None of them have mysql 4 installed... maybe I've had a run of bad luck:-)
I'd be interested in what you think makes php5 not production-ready, though. Is it just for the fact that it is a recent release, or have you experienced/heard of some nasties rearing their ugly head?
Actually, we have a verio blade server also, and it does have mysql 4.
I understand and agree with your point on the requirements of the specs given at the time of proposal, but typically in the jobs I do, portability is an issue, and therefore part of the spec, so I guess it just depends on the client.
My opinion on php5 not being production ready has a lot to do with it being a recent release. I know that from a developer standpoint, its very difficult to bug test _everything_, so thats where users, or i
Life would be so much easier if we could just look at the source code.
-- Dave Olson
Stick with PHP 4 (Score:5, Interesting)
I don't plan to make the switch to version 5 for at le
Re:Stick with PHP 4 (Score:1)
1and1.com [1and1.com] offers php5 support already
2 good ref
Re:Stick with PHP 4 (Score:1)
and just a handful of web hosting companies supporting php5 doesnt make it the defacto as I said.
Portability is really the key here, and in sticking with php4 code, everyone can save headaches from not knowing why certain (php5 only) functions arent working when they "should be". Which mostly just a function of experience. However php is growing very fast in popularity, and because of that, keeping the code as portable as possible is always the best ch
Re:Stick with PHP 4 (Score:1)
The better object model and the try / catch additions alone are what, to me, really sells it
I'm not saying that your points are not valid
Re:Stick with PHP 4 (Score:1)
Have fun with that support call.
And yes, there are some providers taht still have mysql 3.x, however, mysql 4 is the norm, and on MOST servers, which was my point to begin with.
And no, I dont think that PHP 5 is production ready yet either, at least I wouldnt take that chance if I was building for paying clients.
Re:Stick with PHP 4 (Score:1)
Truth of the matter is that I don't think that responsibility falls in my lap. A system is built to a certain requirement spec at the time of proposal
What if we built a java web app and the person sometime down the road wants to switch to a different server/provider that doesn't have java installed/supported? Is that really much different?
In the course of the past 4 months, we've acquired (or upgraded to their new server offerings) about 4 different root servers from 4 different providers
- ValueWeb
- 1and1.com
- MediaTemple
- Verio
None of them have mysql 4 installedI'd be interested in what you think makes php5 not production-ready, though. Is it just for the fact that it is a recent release, or have you experienced/heard of some nasties rearing their ugly head?
Re:Stick with PHP 4 (Score:1)
I understand and agree with your point on the requirements of the specs given at the time of proposal, but typically in the jobs I do, portability is an issue, and therefore part of the spec, so I guess it just depends on the client.
My opinion on php5 not being production ready has a lot to do with it being a recent release. I know that from a developer standpoint, its very difficult to bug test _everything_, so thats where users, or i