On Sat, 2004-03-27 at 19:20, Lukas Smith wrote: > Hi, > > ok since I have seen a few arguments reoccuring I have decided to make a > list of all arguments brought forth. Its in no way a judgement on any > argument listed, nor does it list the arguments in any particular order. > Therefore, the first one to tell me to remove something because the > argument is bogus will have to buy me a "kiba" (cherry-banana juice; fyi > cherry means kirsche in german) next time we meet. This list is just to > keep track of the arguments made, however stupid they may be in the hope > that we dont have to hear it again. > > The list can be found here: > http://www.backendmedia.com/PHP/toStudlyCapOrNotToStudlyCap.txt > > If you think the file name is stupid so be it :-) > > Anyways I have heard reports of people having issues to reach my host. I > hope my sys admin will address this issue promptly in case it persists. > I am sorry for any possible inconvinience. > > Maybe we also need to make a list of all votes, especially separating > the internals developers from the rest as it seems there was also an > argument what side really had the most votes?
Don't take this personally please. My voice doesn't count for much on this list but I do generally read most of the posts. I watched with interest last year when this thing first became an issue, and now I think the whole issue has become retarded. It's like watching a pathetic government debate unfold with for the second time after a consensus was already realized. I think the couple of rogue developers who are against StudlyCaps should suck it in, get with the program, and next time read the mailing lists when they get back from supposed holiday. I mean really, how could the previous StudlyCaps debate have been missed? Were they on holiday for a month? Personally I have a gut feeling some people just chose not to make the move to StudlyCaps with the hope that if they waited long enough (something like after RC1) then they could profess "it's too damn late to make the change". Seriously, I think PHP could only benefit from the consistency now rather than later. With a major version release I think this is more true than at any other time. Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------' -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
