Re: cvs: php-src /ext/bz2 bz2_filter.c
| From: | Hannes Magnusson | Date: | Sun, 15 Feb 2009 04:44:01 +0000 |
| Subject: | Re: cvs: php-src /ext/bz2 bz2_filter.c | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-43049@lists.php.net to get a copy of this message | ||
(private, feel free to take online if you want to)
On Sun, Feb 15, 2009 at 05:00, Greg Beaver <greg@chiaraquartet.net> wrote:
> Hannes Magnusson wrote:
>> On Sat, Feb 14, 2009 at 16:25, Greg Beaver <greg@chiaraquartet.net> wrote:
>>
>>> Hannes Magnusson wrote:
>>>
>>>> On Thu, Feb 5, 2009 at 22:32, Greg Beaver <greg@chiaraquartet.net> wrote:
>>>>
>>>>
>>>>> I really don't give a crap. Change it if you want, I was merging
>>>>> *existing* code in PHP_5_3 to HEAD, not adding new stuff.
>>>>>
>>>>>
>>>> Which is exactly why we have major syncing issues.
>>>>
>>>> HEAD is for development. Stuff should be merged *to* 5.3, not *from* 5.3.
>>>>
>>>> There is no reason at all it should be done any differently.
>>>>
>>>> -Hannes
>>>>
>>>>
>>> seriously, leave the dead horse alone. I promise not to fix things in
>>> the future, the pain it is causing to everyone is not worth my effort.
>>>
>>
>> Fair enough.
>> Then make sure you never ever propose an extension to be bundled and
>> enabled by default with PHP.
>>
>> We agree then to not enabled this extension by default?
>> There are at maximum two people in the entire world who understand WTF
>> is going on with it - AND IT MODIFIES CORE ENGINE things BY DEFAULT!
> ext/bz2 is enabled by default and modified the core engine? That's news
> to me. Or did you think that I was committing to another extension?
I did. I didn't read the filenames, apparently, so I did indeed
thought you were talking about Phar (which scared the frcking life out
of me).
> Grow up.
No, I will not. I have to much "Finnish" (Scandinavian?) blood in my vain ;)
I still find Phar waaaaay to dangerous to _enable by default_ and I
still do not think you are *fit* to handle such extension. (Yes, I did
indeed say it. And I will not apologize for it. I really don't.)
You have your own agenda (just like everyone else), but your focus
isn't on PHP, or the Phar ext.
It really does scare me.
I don't know of anyone that really actually does know what the ext is
capable of (and *I* know it is capable of *great* things. Seriously.
It could swing near the PHP3 "hit" all over again. The ext is
*definitely* a *great* extension.).
Nothing against you personally, but when *noone else* knows wtf the
Phar ext is heading, or anything you do, I find your commits and
communications skills very freighting. Be it Steph or Pierre or
whomever tries to participate. It really does scare me.
On to similar (related) topic:
Did you (or Dmitry) ever communicate?
Once upon a time I heard rumours that "Zend" had already experimented
with an extension "likish" Phar, using 'jar'.
Did anyone ever get "bencharmarks" or whatever from that experiment?
What about compared to Phar?
I really *really* think we should hold off with Phar, at the very
least by default, for at the absolute very least one point release.
The filter extension was *important* extension. Maybe even as
important as (the future will tell) the Phar extension. But I do not
think it is ready.
I really really don't.
Sorry.
-Hannes
(fckit. I am taking this "online". I really do not want Phar
enabled-by-default. Sorry.).