Re: Re: how to deal with php5 only packages

I couldn't agree more. There were complaints earlier about Auth_Enteprise not being active and a lot of it was surrounding my decision on whether or not to use PHP4 or PHP5 for the server end. I decided to use PHP5 being 70% of the code was new and I had not made a php4 release yet. Here at work we are taking them same approach. All new coding efforts are now in PHP5 while we continue to maintain PHP4 applications. --Tony On Wed, 2004-06-16 at 13:21, Hans wrote: > Lukas Smith wrote: > > > David Costa wrote: > > > >> Didn't we agree that the proposal of PHP 5 packages was fine as long > >> as E_STRICT compliant and not stable till PHP 5 is ? > >> You are free to recommend otherwise but I don't think that the > >> approach "PHP 4 works, so why switch" is very progressive. > > > > > > With PHP5 only you are shutting out most of the PHP world. This fact > > will change but I am sure you can come up with better reasons to use > > PHP5 than marking things private? Also your examples have yet to include > > examples where you would actually have to do more planning. > > I think everyone agrees that fewer people will use a PHP5-only package. > David has mentioned that already; I certainly know it's true. To me > this is no reason not to have a PHP5-only package -- especially > considering everyone agrees that these packages will not be stable until > PHP5 is. > > I don't even think a justification other than "I want it to run with my > app that runs under E_STRICT" is necessary. PHP5 is the new version of > PHP. I see no reason to start developing any new software for PHP4 at > this point. I don't care that certain shared host users won't be able > to use PHP5 until later (get a new shared hosting provider! i've been > using PHP5 on my shared hosting provider since PHP5.0.0beta1). > > Hans