On 7/25/2012 7:50 AM, Andrew Faulds wrote:
On 25/07/12 15:19, Lester Caine wrote:
Sherif Ramadan wrote:
... I have no problem
>with it, I use PHP every day, but as explained most PHP-developers
>will have problems and I can say that, because I've more than 20 years
>experience in that. Do you have that?
>
20 years experience in PHP? No, I believe it only ever appeared
publicly about 17 years ago.
20 years experience with developers that have problems? Yes, there's
no shortage of them.
I top you 20 years with 37 years. I was programming in Algol in 1975 (
at Warwick university ). I'm not a programmer, I'm a hardware engineer
who has to program to make systems work. I added PHP 12 years ago to
create web based applications to augment c and Pascal based
applications. Many of the concepts being added make sense only as
extensions to the core code, and don't need to be forced into general
use. Adding tools that have very specialist use should be done as
options, which we can leave out if we want to. The it needs to be
justified switching something on by default. I have no objection to
'new facilities', but only if I can also switch them off ...
Yawn. Any time someone pulls out the "years of experience" card, it
just means to me that they don't have any further arguments worth
listening to and there's also a pretty good chance that they don't
actually know how to do their job right - in this case, developing
software - but this principle applies to all industries (e.g. recently
dealt with a flooring company who acted in a similar manner). Lester
said, "I'm a hardware engineer who has to program to make systems work"
- the key phrase there that sticks out to me is 'has to' which implies,
on at least a subconscious level, that he doesn't actually enjoy writing
software. Hardware guys tend to not like writing software (they would
much rather be soldering something) and the reverse tends to be true as
well. So do you want someone like that dictating the future of PHP,
that which is a software application? Probably not.
Actually, I was initially against generators in PHP myself. Then, as I
was writing my rant about adding useless crap to the language and, as I
carefully thought about my rant before sending it, I actually determined
that *significant application performance improvements* might be a key
benefit. So I ended up not replying at all. I really think we might
see actual performance improvements here but we'll need benchmarks to
back it up and it should be a primary goal clearly spelled out in the
RFC somewhere near the beginning of the document.
Eh, what? "Switch them off"?
What on earth do you mean? "use noGenerators" and then break tons of
third-party code relying on it? Or do you think you're forced to use them?
I don't understand, sorry.
A feature's existence doesn't mean you're forced to use it. Did the
introduction of short array syntax force you to use [] instead of array()?!
--
Thomas Hruska
CubicleSoft President
Barebones CMS is a high-performance, open source content management
system for web developers operating in a team environment.
An open source CubicleSoft initiative.
Your choice of a MIT or LGPL license.
http://barebonescms.com/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
