On 21 February 2013 16:30, Rasmus Lerdorf <ras...@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/
