2.) Probably a better idea, just click that DELETE button on any
emails you don't feel like reading or responding to. I find that, in
a case study performed by myself just now, it takes me about a
half-second to achieve success with this method.
Against my better judgement, I'm jumping into this thread...
The problem with simply deleting mail you don't want to see is the
same as "just delete the spam you get"; it's one of signal-to-noise,
and the delete button worked until you get to that magical threshold
where it seems like all you're getting is junk and accidentally delete
the good stuff.
Take this thread for example. I find it very interesting as there are
many problems with PHP development as it currently stands (social
problems), and I've been working on coming up with a solution for just-
short of a year now (as many of the core members will attest, as I've
had offline, face-to-face conversations with them about this).
However, because Jani's original post was buried in the middle of YET
ANOTHER ridiculous debate on the "best" namespace operator, I actually
had to go back to my trash and dig out the original mail after seeing
Greg's reply and quoted text. I would never have seen it because I got
trigger happy because almost all of this thread was absolute junk.
I don't yet have a solution, not would I try to force it upon anyone,
but I do hope to propose one in the coming months. One that does
involve making internals read-only for non @php.net holders, but also
provides a clean and reasonable path for non-contributors to
contribute, and somehow weeds out the gimme-gimme freeloaders (note:
yes, there are [EMAIL PROTECTED] holders that are not freeloaders).
S
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
