Rasmus,
On Wed, January 29, 2014 16:37, Rasmus Lerdorf wrote:
> On 1/29/14, 7:00 AM, Anatol Belski wrote:
>
>> please look here
>>
>> https://github.com/weltling/mongo-php-driver/compare/mongodb:master...m
>> aster
>>
>> two hours of work and it's about 70% of the porting, compiling with 5.5
>> and str_size_and_int64. This is the hard caliber of course.
>
> And that is only 70%?
>
>
> This is a massive effort that will have to be done on each of the 1000+
> extensions out there. It is going to take years before the extensions catch
> up and therefore will slow PHP 5.6 adoption to a crawl. This is not
> something that belongs in a point release.
>
> -Rasmus
>
70% done in two hours on such a monster? The last say 5-10% might take
some longer. Say for that caliber - 3 workdays (port, fix beyond, test) to
be done is realistic. The start into porting Zend, main and other very
core was very long and painful, but doing the same with extensions now is
an exponential speedup.
Where comes the number 1000+ from? Last year what I could see on PECL -
about 300 extensions, about 40% really active. Clear, a number is also not
in PECL, like GPL'd and so, but 1000? Massive effort is rather a big
exception. And it's not like one would keep off and amuse himself while
the exts are dying.
Reading such stats http://w3techs.com/technologies/details/pl-php/5/all
I
wonder what is with the 5.5 adoption? If that data don't lie, despite the
amount of work done on 5.5, including PECL, it's not that wide spread as
one would wish. At least, it's being adapted slowly. Do we expect 5.6
adoption to be any faster?
What I'm conducting to is that - the porting concerns are very
overestimated, the adoption of 5.6 might go much slowlier as one could
wish. And the last which should be the first - the RFC solves platform
issues which retard the PHP improvement as the whole.
Regards
Anatol