Re: Internals read-only

From: Date: Thu, 13 Dec 2007 16:44:47 +0000
Subject: Re: Internals read-only
References: 1 2 3 4 5 6 7  Groups: php.internals 
Request: Send a blank email to internals+get-34020@lists.php.net to get a copy of this message
Richard Quadling wrote: > On 13/12/2007, Jochem Maas <jochem@iamjochem.com> wrote: >> 1. most people reading the internals list already subscribed to general >> 2. general is in no way suitable for the kind of discussion currently >> occuring on internals - the difference between internals and general is akin >> to the difference between fine art and drawing with crayons. > > I'm SURE you are not implying that those that use the PHP language > (rather than the developers of the PHP language) are some how more > infantile and can only use crayons rather than wielding the fine > brushes that create the art of the language itself? no not at all, I was implying that the gross of the traffic on generals are questions related to problems people have with stuff like register_globals - aka full-on noobs, nothing wrong with that and actually I quite like to help most of them (as do a fairly small but very active group of experienced, well-armed phpers) ... it's just not the place to discussion the finer/complex details of php functionality implementations. imho. the crayon metaphor was actually an in-joke for the guys who are regulars on the generals list. > > I would say that we (those that write PHP code) are your clients and > as the client is __ALWAYS__ right, you should drop namespaces, add in this context I am the client - and I have been proven wrong many a time, even then I'd rather not have my voice taken away completely ... and you never know if I might one day say something useful. ;-)

« previous php.internals (#34020) next »