I guess you've haven't grasped the universal constant when it
comes to judging the efficacy of technological solutions:
It Depends.
If you're running client as a weekend warrior and not a deployed
server in a production environment then I would say breaking it due
to an OS update isn't mission critical.
The OS was supplied with 64bit capabilities for a reason and in a
real server environment it makes practical sense to utilize the
advantages offered from running in a 64bit environment.
I always find it interesting to see people throw about the adjective
"real" in defense of their particular dogma.
YOUR situation may compel you to decide that this is not the a
"recommended path", however there are others in the world who have
differing circumstances where this particular approach works out
absolutely brilliantly.
Off-hand I don't know of any real deployed production servers that
use a thinned apache since the benefits of running in 64bit are
much more attractive and this is the general consensus and not my
personal situation.
Please provide us with a real-world example of the practical benefits
of running a PHP application under 64-bit mode Apache 2 in the pre-
forked model.
And of course you don't know of any servers that fit the above model,
because you have a limited view of the rest of the world. Or do you
believe that you are omniscient and that Your Way is the only way to
do it "Right"?
is reason enough to not do it
have to outweigh the cons considerably and that is why it's not a
recommended procedure.
The better solution
doing it the right way is what I recommend
doing it right the first time
If you have to ask then it's obvious you don't understand why.
he do it properly now
Get over yourself.
There are others in the world that have differing opinions and
estimations of risks/rewards.
