On Fri, Jul 20, 2012 at 10:33 AM, Lester Caine <les...@lsces.co.uk> wrote:
> > And still seems to be the best way even to 'investigate' this? I still > have not had any explanation of what is wrong with ArrayObject? Certainly > any changes need to be mirrored identically in that anyway? > > Also perhaps I am just too set in my ways, but while I understand the > needle/haystack complaint, I don't see a major problem that needs > everything changing. Perhaps add the odd alternative as that would be the > only BC fix anyway? > > Most of the people who complain about these things are not going to change > TO PHP anyway so why keep messing things up for those of us who's > livelihood depends on productivity in PHP! > > I don't see this as "solving a major problem", sure most of us relies on IDE's or shear memory to know where needle/haystack should be. But that does not invalidate that this "feature" is a nice syntax sugar, just like short arrays and other things were. Also this does not have to affect anyone's livelihood or productivity, it will fuel who wants to use it, and maybe the new generation of PHP devs. I for sure would change from using most string functions to it, but not 100% of the time, so really face this as being syntax sugar, which i love, i'm very much focused on code readability and this makes a lot of sense from context and ease of understanding, it does not change everything, but its a nice to have. Technologies and languages evolve, i think its valid to look a new resources to give people more choices and it goes a long way into making learning PHP easier for new devs who don't have to suffer our organic api, which feels confortable for us who have been at it for over 10 years, but is enough of a bother to new people I guess. Anyway, i would love to see this as a alternative, not a replacement, for some of the string functions and similar things -- Rafael Dohms PHP Evangelist and Community Leader http://www.rafaeldohms.com.br http://www.phpsp.org.br
