On 27.10.2008, at 23:27, Stanislav Malyshev wrote:
this is how PHP got its huge userbase. we let people grow with
their needs.
And how exactly it serves the needs of people by secretly making
their applications orders of magnitude slower, and then saying "oh,
that's because you failed to read paragraph 16.4.5.1 in the manual,
you should really read that paragraph before pretending to be PHP
programmer!". Good environment or does what you want it to do, or
fails, explaining to you why it doesn't work - it doesn't do it half
way half broken and then blames you for not reading some obscure
note in the manual. That's not how I see helping.
ok this might be a shock for you .. but the vast majority of our user
base does not have a performance problem (thats not to say we need to
waste their CPU cycles .. we all love the planet).
then as we are suggesting they will not have to read a manual. in our
proposal they can use all the existing books, examples on PHP, migrate
their code easily to namespaces and things will just work. if they
advance beyond the point of absolute n00b, they will learn to look for
E_NOTICE and by that time they will know how to fix their performance
issues (if they have any) without having to open a manual.
in your scenario, all examples in the world will mysteriously break
when they are used inside a namespace (which they might have gotten
from another example or some inherited code).
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
