Ilia Alshanetsky wrote:
On 4-Nov-06, at 11:18 AM, Christian Schneider wrote:
Ilia Alshanetsky wrote:
Avoid common namespaces and you'll make your application futureproof.
I'm still wary of this approach because it puts the burden on 99% of
the code to be written (applications) instead of a small, controllable
subset (core and libraries).
Translation: blame other people...
I'm not sure what you mean here. I was just doing a head count on who
has to come up with save names: A few core developers or all of the PHP
users.
The language should ALWAYS have the best names possible to simplify
development, because that means convenience for majority of users. No
While that's certainly true (and part of me is even thinking it is the
right approach) it means that each and everyone writing PHP code (which
means a big number of people with all different levels of experience)
has to care about naming. So it makes the language a little less simple
to use. That's all I'm saying.
matter how popular your app, PHP, the language is still hundreds if not
thousands of times more popular and as such needs of many outweigh needs
of the few.
A little thought experiment: Let's assume the number of application
classes (and the usage of those classes) is on average higher than those
of the core classes. Would that change the situation?
You can use old PHP too, or modify the source code, it is "open source"
after-all.
Come on, that can't be the solution. Think about hosting companies for
example.
Don't get me wrong: I'm not saying you're wrong, I'm just trying to
provide another point of view on the topic here which should be
considered IMHO.
- Chris
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
