Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66121
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <51263D89.5040308@lerdorf.com>
References: <alpine.DEB.2.02.1302201817350.5312@whisky.home.derickrethans.nl>
 <678597E6-E3A8-42E0-8DFC-F8382C9DFB41@strojny.net> <8d4e991084a1313844910ec0168eacdf@mail.gmail.com>
 <CAEZPtU5RZbVJS0txYRxxpTXzvk0ZvQdZBfx7qHTYwAd4cyn6Rw@mail.gmail.com> <51263D89.5040308@lerdorf.com>
Date: Thu, 21 Feb 2013 16:54:41 +0100
Message-ID: <CADyq6s+W+UtEprrTVQ4r8CPO0fQpSeP8neO8edfsG3z4qHOzOQ@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Pierre Joye <pierre.php@gmail.com>, Zeev Suraski <zeev@zend.com>, Lars Strojny <lars@strojny.net>, 
	Derick Rethans <derick@php.net>, PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=14dae9cdc487ed8e2a04d63e18ae
Subject: Re: [PHP-DEV] Give the Language a Rest motion (fwd)
From: ocramius@gmail.com (Marco Pivetta)

--14dae9cdc487ed8e2a04d63e18ae
Content-Type: text/plain; charset=UTF-8

On 21 February 2013 16:30, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> In the slice of the "community" where I spend most of my time
>

No hard feelings, but it would be awesome if that part of the "community"
(the one that basically avoids social coding as far as I can see, not to be
taken as a sin, but still "meh") didn't just try to hold back PHP because
of business decisions based on obsolescence.
If there is some momentum to get change, I see these big brakes set by
people who don't even express their opinion nor get interested in newly
developed packages over here.
It would already be nice to have them provide their opinion, assuming it
goes a bit deeper than "YAGNI".

No BC changes is basically impossible if you want to get better software:
improvement comes always with changes.

I can absolutely understand that the core team does not have enough human
resources to think about new functionality, and probably not even
maintenance (I even feel like a stranger forcing his own ideas in here,
since I also have no C-fu), but why would this stop things from being
suggested?
If you don't have time for a feature, then that's perfectly ok: just vote
"NO".

Don't sell us the "YAGNI" or "additional complexity" story: annotations and
property accessors already demonstrated that there are use cases that even
bring performance improvements.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--14dae9cdc487ed8e2a04d63e18ae--